Most accessibility bugs pass every test and look fine in a demo. The first report often comes from a customer who couldn't finish checkout, and plenty never write in at all.
The ones I keep seeing in pull requests: a div with onClick that Tab skips, an icon button a screen reader announces as just "button", and a label not tied to its input, so the field has no name.
A quick test before a release: unplug the mouse and try to finish your main flow with only the keyboard. It takes five minutes.
Has one of these ever cost you a user or a deal? And how do you catch them now: a linter, axe in CI, manual testing, or customers telling you?
Top comments (1)
Accessibility failures often show up as silent abandonment rather than a support ticket. Testing critical flows with keyboard navigation, zoom, screen readers, and real content catches issues early—and gives product teams a clearer picture of whom a friction excludes.