Every accessibility audit we've run on a launched product turns up the same root cause: the components weren't built with keyboard and screen-reader support from the start, so every fix now touches code that's already shipped and already depended on.
The fix is boring and it works: bake focus states, semantic HTML, and ARIA labeling into the base component library, so every team building on top of it inherits accessibility instead of retrofitting it.
It's meaningfully cheaper to get this right once in a shared Button component than to fix it in forty places it got copy-pasted into.
- Accessibility
- WCAG
MB
Written by Maria Barwaniwala
Design Director at HASANI.
