What Accessibility Is
Accessibility is designing interfaces so all people — regardless of ability, device, or context — can perceive, understand, navigate, and interact with them.
Accessibility is not a feature you add after launch. It is a structural property of an interface — one that is either present from the first decision or absent throughout.
What it is
Accessibility means that an interface works for people across a full range of abilities, devices, and contexts. The Web Content Accessibility Guidelines (WCAG) organise this into four principles: content must be perceivable, interface components must be operable, information must be understandable, and content must be robust enough to work with current and future assistive technologies. These four principles — known as POUR — are the structural definition of accessible design.
What it is not
Accessibility is not synonymous with “adding alt text” or “making it work for blind users.” It covers cognitive load, motor control, hearing, vestibular disorders, situational impairments, and the wide range of assistive devices people use. It is also not a checklist you complete once. Every design decision either improves or degrades it.
Why it matters structurally
A page that is structurally inaccessible is not merely harder to use — for many users it is completely unusable. Screen readers, keyboard navigation, and voice control all depend on the underlying structure of an interface. A visually polished page with no semantic structure communicates nothing to a screen reader. Form — in this sense — determines function absolutely.
The mistake
Treating accessibility as an audit phase at the end of a project. By that point, the structural decisions that would have made accessibility straightforward — semantic HTML, logical heading order, sufficient contrast — have already been made in inaccessible ways. Retrofitting costs far more than designing correctly from the start.
The takeaway
Accessibility is a design quality, not a compliance task. When you treat it as a constraint from the beginning — like responsive layout or performance budgets — it shapes better decisions throughout. Start with who accessibility serves to understand the full scope of users your decisions affect.