there
A problem markup and interaction pattern I encounter a lot is a result of people (understandably) following a misleading example from the W3C.
Apple’s World Wide Developers Conference (WWDC) opening keynote is one of the big highlights in my calendar. Here are the bits that stood out to me.
At some point a third party will audit the accessibility of your product; being strict now makes that process smoother and far less stressful.
Hierarchical tables can be a lot to understand, particularly for screen reader users. Here’s how to tackle hierarchy when it can’t be avoided.
Accessibility buy-in from senior leadership can be tough; real change comes from the people who design and build.
Producing accessible software means continually questioning your own habits and assumptions about how people interact with it.
Marking up navigation is pretty straightforward, but here’s a nice reminder on how the aria-label should be written.
Shipping something inaccessible is rarely a shortcut; it’s usually a debt.
The more I learn about accessibility, the harder it is to look back at some of my old work; but that cringe is a useful measure of progress.
For years and years, developers have had to come up with all sorts of creative workarounds to style select elements, but now you can do it properly.





