Fixing the timeline: Accessibility before the bugs exist

We used to fix accessibility last. A component would ship, the bugs would roll in, and we'd go back and patch them. But those components were never built for accessibility, so the fixes broke other things and took weeks. Every new feature could undo our work.

So we did something bold: we went back in time. For our next generation of components, accessibility comes first — not last.

Here's how we did it. Every component now starts with a simple accessibility plan. Each one matches a proven, accessible pattern and a real HTML or ARIA role. Then automated and manual tests keep it that way, so bugs can't sneak back in.

Come see how moving accessibility to the start let us stop fixing the past — and start building a better future.