Accessibility

Letter A

The practice of designing and developing digital products so people with disabilities can perceive, understand, navigate, and interact with them. In UX, it turns inclusion into requirements that can be verified from the start.

Updated:

Working definition

Digital accessibility is the practice of designing and developing products so people with disabilities can perceive their content, understand it, navigate it, interact with it, and complete the tasks they need.

It does not mean creating a special version for a separate group. It means identifying barriers in the product and avoiding accidental requirements for a particular way of seeing, hearing, moving, communicating, or processing information.

In UX, accessibility turns that intent into observable and testable decisions: keyboard navigation, semantic structure, visible focus, alternatives for non-text content, understandable instructions, sufficient contrast, useful error messages, and compatibility with assistive technologies.

What a11y means

A11y is an abbreviation of accessibility: eleven letters sit between the first “a” and the final “y.” It is not a different discipline or a level of conformance. It is simply a short name commonly used in design and development.

Design against barriers, not people

Disability can interact with permanent, temporary, or situational barriers. Someone may be unable to see an image, hear audio, use a mouse, respond within a short time, or understand dense content. The same product may also be used in bright sunlight, with one hand occupied, or in a noisy environment.

The goal is not to treat all these experiences as equivalent. It is to recognize when a product explicitly or accidentally requires a particular ability. The operational question is: which part of this experience stops working when the way someone perceives, understands, or interacts changes?

The four WCAG principles

WCAG organizes its guidance around four principles. Content and interfaces should be:

  • Perceivable: information can be obtained in more than one way, such as images with text alternatives and video with captions.
  • Operable: functionality works with different input mechanisms, including a keyboard, without focus traps or time limits that cannot be extended.
  • Understandable: content, navigation, and messages use predictable language and behavior.
  • Robust: structure communicates names, roles, states, and relationships to browsers and assistive technologies.

WCAG success criteria support conformance evaluation, but they do not describe every human need. They are a technical and testable foundation, not a replacement for understanding people.

How accessibility changes UX work

During discovery

  • Include people with disabilities in research when they are part of the product population.
  • Ask about strategies, tools, and actual barriers rather than diagnoses alone.
  • Account for device, connectivity, noise, lighting, fatigue, and available time.

During design

  • Keep hierarchy and journeys understandable without relying solely on visual presentation.
  • Design focus, error, loading, success, and disabled states.
  • Do not use color, position, sound, or motion as the only way to communicate meaning.
  • Support zoom, reflow, and preferences such as reduced motion.
  • Write labels, instructions, and messages that explain what happened and how to continue.

During development

  • Prefer semantic elements over recreating their behavior with generic components.
  • Preserve a coherent reading and focus order.
  • Expose names, roles, values, and status changes correctly.
  • Check the product with a keyboard and relevant assistive technologies.

During validation

Automated tools detect some problems, but they cannot determine by themselves whether an experience is accessible. Combine automated checks, manual review, and testing with real people.

Accessibility, usability, and inclusive design

Usability asks whether an experience supports effective, efficient, and satisfying task completion. Accessibility asks whether people with disabilities can access and operate that experience without avoidable barriers.

Inclusive design is a broader approach to recognizing diversity and exclusion throughout the process. Accessibility contributes standards, requirements, and evaluation methods focused on access for people with disabilities. They reinforce one another, but they are not synonyms.

Anti-patterns

  • Reviewing accessibility only after the architecture and components are fixed.
  • Reducing accessibility to color contrast.
  • Treating an automated score as complete certification.
  • Adding an overlay that promises to repair the interface without fixing its underlying barriers.
  • Discussing people with disabilities without including them in research and validation.

Quick check

  1. Can someone complete the task using only a keyboard?
  2. Is focus visible and ordered predictably?
  3. Does the structure still make sense without visual styling?
  4. Do images, audio, and video provide appropriate alternatives?
  5. Is color, position, or sound the only way to communicate anything?
  6. Are errors identified, with clear instructions for recovery?
  7. Does the content support zoom, reflow, and reduced motion?
  8. Did we test with people who use assistive technologies?

Short definition

Digital accessibility removes barriers so people with disabilities can use a product. It is designed from the start, translated into testable requirements, and validated through standards, human review, and lived experience.