Accessible design
Accessibility is a product decision, not a final check
The most valuable accessibility choices are often made before components, audits, or compliance reports enter the conversation.
17 July 2026 · 4 min read
Accessibility begins with scope
An accessibility audit can identify important technical issues, but many barriers are created earlier: in the choice of workflow, the amount of information requested, the language used, and the assumptions made about attention, memory, confidence, or device access.
If a journey asks someone to understand unfamiliar terminology, retain information across several steps, or recover from an error without clear guidance, technically valid markup will not make the overall experience inclusive.
Design the task before the interface
A better starting point is to examine what the person is trying to achieve and what could make that difficult. This changes the design conversation from adding accessibility features to removing unnecessary barriers.
- Can the task be completed in shorter, understandable stages?
- Is important context available at the moment it is needed?
- Are errors explained clearly and recoverably?
- Does the experience remain usable with keyboard, zoom, reduced motion, and assistive technology?
Compliance matters, but it is not the whole ambition
Standards provide an essential baseline and a shared way to test implementation. The stronger product decision is to combine that baseline with an understanding of the people, pressures, and environments around the task.
Accessibility works best when it is part of product strategy, content, interaction design, engineering, and quality assurance from the beginning.