Accessibility, usability, and universal design

Why it matters

Accessibility, usability, and universal design are three concepts that are frequently confused or used interchangeably — even by practitioners. Clarity about what each term means, and how they relate to one another, is essential for CPACC and for professional communication with clients, developers, and stakeholders. (BoK p. 36)

Accessibility

Accessibility asks a threshold question: can a person with a disability use this at all? It is typically operationalized through standards — WCAG success criteria, Section 508 requirements, or national equivalents. Meeting accessibility standards is a pass/fail evaluation at a defined level. (BoK p. 36)

A website is accessible (at WCAG 2.1 AA) if it meets all Level A and Level AA success criteria. That is the entirety of what “accessible” means in a technical context. It says nothing about whether the site is easy, efficient, or pleasant to use — only that it can be used by people with disabilities.

Accessibility is a prerequisite. A product that cannot be accessed by a screen reader user is not accessible, regardless of how well-designed it is in other respects. The goal is an equivalent experience: a user with a disability should be able to achieve the same outcomes with the same quality as a non-disabled user, even if the method differs.

Usability

Usability asks a different question: how well can users achieve their goals? The ISO 9241-11 definition organizes usability around three dimensions: effectiveness (can users complete the task?), efficiency (how quickly and with how much effort?), and satisfaction (how do users feel about the experience?). (BoK p. 36)

Usability is a spectrum, not a threshold. Products can be more or less usable; there is no single pass/fail standard for usability the way there is for accessibility. And usability applies to all users — not just people with disabilities. The target group matters: usability findings from non-disabled participants do not automatically transfer to users with disabilities, which is why inclusive user research must include participants from the full target group.

A critical insight: an accessible product is not necessarily usable. A screen-reader-compatible form that takes 45 steps to complete a simple task, generates cryptic error messages, and offers no help is accessible in the technical sense — but has poor usability. Accessibility is necessary but insufficient.

The relationship: UD as the encompassing goal

Universal design encompasses both accessibility and usability within its broader ambition: designing products, services, and environments that work well for the widest possible range of people. (BoK p. 37)

The BoK uses an overlap model to represent this relationship. Accessibility and usability are partially overlapping concerns — they share the goal of enabling people to use products effectively — but neither fully contains the other. Some usability improvements are not accessibility requirements; some accessibility requirements do not improve usability for non-disabled users. Universal design is the larger goal that holds both together.

This model matters for practice: organizations focused only on accessibility compliance may create products that are technically accessible but poor to use. Organizations focused only on usability testing with non-disabled users may create products that are pleasant for most but inaccessible to some. Universal design requires attending to both, for the broadest range of users.

User experience

User experience (UX) extends the concept further — beyond whether tasks can be completed, to the totality of perceptions, emotions, and attitudes a person develops through use. A product can be accessible, usable, and still have a poor UX: cold, clinical, unsatisfying, or anxiety-inducing. (BoK p. 37)

For CPACC purposes, UX is introduced as context. The BoK’s primary concerns in Domain 2 are accessibility and usability, with UX as the broader landscape in which they sit.

Real-world example

A government tax filing website passes a WCAG 2.1 AA audit — a screen reader can access every element, form fields are labeled, errors are announced. It is accessible. However, the navigation requires six clicks to reach the filing form, error messages say “Error 422” without explanation, and completing a simple return requires 20 steps across three pages. A screen reader user can access every step — but the task is arduous and abandonment rates are high.

A usability study adds: plain-language error messages, a streamlined three-step process, and a progress indicator. These changes improve the experience for all users — disabled and non-disabled alike. That is the universal design approach: designing for effectiveness, efficiency, and satisfaction for the full range of users.