Design · Apr 2025 · 6 min read
Accessibility Is Not a Phase — It's a Standard
The details that make a site usable with a keyboard, a screen reader or shaky hands are the same ones that make it feel precise for everyone.
Accessibility still gets filed under “nice to have” — the compliance pass, the checkbox sprint before launch. We see it completely differently. The disciplines that make an interface work for someone navigating by keyboard are the same disciplines that make it feel precise for someone navigating by mouse. Accessibility is not charity work bolted onto design; it is design, done properly.
The craft overlaps are everywhere
A visible, well-designed focus state is indistinguishable from good interaction design — you are simply answering “where am I?” at all times. Semantic HTML is not bureaucracy; headings that form a real outline are the same structure that makes a page scannable for everyone. Labels tied to inputs, honest button elements instead of clickable divs, contrast that survives sunlight on a phone — each one is simultaneously a requirement and a quality upgrade.
Motion preference is the clearest example. Respecting prefers-reduced-motion forces a question every animation should answer anyway: what information does this carry? When the movement is gone and the meaning survives, the design got better, not just safer. Constraint, as always, was the editor.
A site that works without a mouse, without motion and without perfect eyes is simply a site that works.
Cheap early, expensive late
The economics are lopsided in one direction. Alt text written while the image is chosen costs seconds; retrofitting it across a finished site costs days. Heading structure decided at wireframe stage is free; restructuring a built page is surgery. Keyboard traps caught in a component library take minutes; discovered in launch week they take a war room. Every accessibility practice is dramatically cheaper at the moment it feels least urgent.
And the audience is not an edge case. Permanent, temporary and situational impairments cover most people most of the time — an arm in a cast, a bright office, a loud commute, simple fatigue. Designing for the edges of ability is indistinguishable from designing for reality.
So we folded the standard into the pipeline itself: semantic structure by default, keyboard testing as part of feature done, contrast checked in the token system, motion gated behind preference. Nothing heroic, no audits of shame — just craft, applied consistently. That is what a standard is.