A recorded session using Tab, Shift+Tab, and Escape through a real product. Accessibility bugs are easy to miss because they do not show up in screenshots. The only reliable way to find them is to use the interface the way assistive technology users do.
Sample footage: Tears of Steel, an open movie by the Blender Foundation, released under a Creative Commons licence.
What users actually experience
Most of the problems we found came from custom controls that looked like buttons but were built from generic elements. Switching to native elements fixed focus, keyboard support, and announcements in one step.
- Use native elements before ARIA.
- Every interactive element needs a visible focus style.
- Test with a keyboard before every release.
- Keep text contrast at 4.5:1 or higher.
Automated checkers catch roughly a third of the issues. The rest need a keyboard, a screen reader, and a few minutes of patience. We now budget that time into every feature estimate.
Program testing can be used to show the presence of bugs, but never to show their absence!
Edsger W. Dijkstra, Notes on Structured Programming, 1970
We run this in production at a fairly large scale and can confirm the caveats are real.
I would push back a little on the second section. In our monorepo the trade-off went the other way.
+1, this matches what we saw after the migration.
This is exactly the write-up I needed this week. We hit the same wall last sprint.
The part about naming things made me laugh, then made me go rename three functions.
Our accessibility audit flagged exactly this last month. I wish I had read this first.
We tried something similar in 2023 and rolled it back. Curious whether the tooling has caught up since.
Solid write-up. The warning about caching bit us hard last year.
Counterpoint: for small teams the simpler approach in the first section is usually enough.