We often talk about accessibility as something you can simply switch on at the end of a project—a box to tick at launch or an optional mode in the settings menu.
But accessibility isn’t something you add at the finish line. It’s a foundation you build from the start.
Why the “toggle” mindset fails
- Retrofit rarely works well: Adding accessibility after launch often leads to expensive fixes and less effective experiences.
- It treates access as optional: Seeing accessibility as an "extra" sends the message that some users matter less.
- It ignores the bigger picture: Accessibility isn’t just about screen readers or contrast ratios—it’s about how your entire product supports different abilities, contexts, and needs.
Accessibility as system design
Accessibility should influence every decision—from branding and product strategy to engineering and testing. Instead of treating it as an afterthought, use it as a lens for better questions:
- Does typography remain legible and balanced at any size?
- Do our color choices maintain contrast across themes and brands?
- Are interaction patterns consistent, predictable, and forgiving when mistakes happen?
- Is motion or animation helpful, or could it cause discomfort?
- Do error messages guide users clearly, without blame?
- Is copy written in plain, respectful language for both first-time users and experts?
- Does the product still work when internet connections are slow or unreliable?
- Can users relying on keyboard navigation, speech recognition, or screen readers complete key tasks without barriers?
- Do we offer alternatives—captions, transcripts, alt text—so information is always accessible?
When these considerations are built into systems—tokens, components, guidelines—accessibility becomes part of the product’s DNA, not just a one-off fix.
Shifting the conversation
Instead of asking, “Did we make it accessible?”, ask, “How does this system enable access for everyone by default?”
This shift moves accessibility from a compliance checkbox to the heart of good design.
Accessibility isn’t a toggle. It’s how we build systems that welcome, guide, and include. It’s ongoing practice. It’s care. It’s good design.