The third edition of The Accessibility Show with Nathan Wrigley of WP Builds dropped early this morning, and I have to say that I’m really enjoying this show. First of all, chatting with Nathan is a bright spot in my day every time – he really is the nicest man I know. But I’m also finding it fascinating to go into the WordPress showcase and pick out just one issue to highlight as an accessibility problem. Focusing on one issue […]
Continue reading “The Accessibility Show #3: Newsletter Sign-ups” »Category: Web Development
Hover Color Contrast Bookmarklet
This past weekend, I was looking at a WordPress trac ticket about hover color contrast in the admin. One of the things that was frustrating about this ticket is the amount of labor expected in testing – because accessibility tools mostly test the page as is. It’s certainly possible to implement automated tooling that can look at all of that, but introducing a whole new suite of tests to WordPress core was outside of my area of expertise. But a […]
Continue reading “Hover Color Contrast Bookmarklet” »The real added costs of accessibility
For many years, I’ve seen repeated – and have myself repeated – the idea that an accessible website is not more expensive. That idea comes with a notable caveat. That caveat, to sum it up, is that it is not more accessible to build an accessible website from scratch than it is to build an inaccessible site from scratch. Building from scratch. When was the last time you built a website from scratch? What does it mean, in 2022, to […]
Continue reading “The real added costs of accessibility” »Accessibility is Equality
I’ve long felt that accessibility is conceptually simple, and technically difficult. I’ve believed that if you can convey the fundamental concept of digital accessibility to somebody, everything else can be extrapolated from principles. That doesn’t mean that somebody would conform to accessibility guidelines at any level based on this. Reaching for accessibility by application of principles doesn’t necessarily yield the same result as what you’ll find in accessibility guidelines, but – in principle – should still encourage a sound interpretation […]
Continue reading “Accessibility is Equality” »Everybody should write a CMS
I’m not joking, although I’m sure that’s the first impression from this post’s title. But there’s a crucial caveat: everybody should write their own JavaScript framework or content management system; but very few should ever let their tool get used. There’s an enormous learning value in programming a large, complex system. You get a strong sense of accomplishment, while learning just how complicated it is to create a flexible theming system, menu structuring tool, and content editor – let alone […]
Continue reading “Everybody should write a CMS” »