Who Accessibility Serves

Most designers imagine accessibility as serving a small group of users with permanent disabilities. The actual population is much larger — and at some point includes everyone.

The three categories

Disability is not a fixed state. It exists on a spectrum with three practical categories. Permanent disability is a long-term condition: a user who is blind, deaf, or has limited motor control. Temporary disability is situational but time-bounded: a user with a broken arm, recovering from eye surgery, or managing a short-term illness. Situational disability is context-driven: a user holding a phone in bright sunlight, in a noisy environment, or on a slow connection. The same interface design decisions affect all three groups.

Why this matters

When you design for permanent disability, you improve the experience for temporary and situational users automatically. Captions on video help the deaf user, the user in a noisy office, and the user who cannot play audio. Sufficient contrast helps the low-vision user, the user in direct sunlight, and the user on a low-brightness display. Keyboard navigation helps the user with motor impairment, the power user who prefers keys, and the user whose trackpad is broken.

The design implication

Accessibility is not a niche requirement. It is the condition under which an interface is genuinely usable across the real circumstances of real users. A rough estimate suggests that at any given time, roughly one in five people experience some form of disability that affects how they interact with digital interfaces. Design exclusively for the ideal user in ideal conditions and you exclude a significant portion of your audience.

Cognitive accessibility

Cognitive accessibility is the most under-addressed area of inclusive design. It covers the range of cognitive differences that affect how people interact with interfaces: memory and recall limitations, attention and distraction, reading comprehension, processing speed, executive function, and conditions including dyslexia, ADHD, and acquired cognitive impairment from stroke or injury.

This is not a fringe concern. Cognitive differences are more prevalent than visual impairment, and they interact with every other category. More practically: users under stress, fatigue, or divided attention — which is everyone, at some point — behave more like users with permanent cognitive impairment than like users in ideal conditions.

In practice, cognitive accessibility looks like: plain language (short sentences, common words, one point per paragraph), consistent navigation (the same controls in the same places on every page), specific error messages (what went wrong and how to fix it, not just that it failed), adequate time (session timeouts with warnings), minimal distraction (no auto-playing media, no unexpected movement), and chunked complexity (multi-step processes broken into labelled stages with a progress indicator). These decisions make interfaces better for everyone, which is the pattern that defines good accessibility design.

The mistake

Assuming that because an interface “looks fine” in a single context — desktop, mouse, full screen, good lighting — it works. Users are not in controlled conditions. They are on mobile in sunlight, navigating with a keyboard, using a screen reader, or managing cognitive load from an unrelated source. The question is not whether your interface looks good in the demo. It is whether it works under real conditions for real people.

The takeaway

Designing for the full range of users is not an act of charity — it is the correct framing of what “working” means. The next step is understanding how the industry has standardised this into a testable framework: the WCAG guidelines.