# Accessibility

Digital accessibility means designing and developing products so people with disabilities can perceive, understand, navigate, interact, and contribute.

- Type: principle
- Domain: Experience & interface
- Level: Foundational
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/accessibility/>)

## What it means

Accessibility removes barriers created by product decisions across visual, auditory, motor, speech, cognitive, neurological, and other experiences. It spans content, interaction, code, media, procurement, support, and ongoing evaluation rather than belonging to a single checklist or specialist.

## Why it matters

Inaccessible products can block essential tasks and exclude users from information, work, services, and participation. Building access into routine design and engineering also produces clearer structures, more input options, and more resilient experiences.

## When to use it

Apply accessibility throughout discovery, design, content, development, procurement, testing, release, and maintenance. Prioritize it especially for essential tasks and when changes introduce new interaction models, media, or third-party technology.

## How it works

1. Include disabled people and relevant access needs in research and decision-making.
2. Use semantic structures, clear content, flexible presentation, and multiple input methods.
3. Apply appropriate standards and platform guidance as testable baselines.
4. Test early with keyboards, zoom, settings, automated tools, and assistive technologies.
5. Test complete tasks with disabled participants, not only individual screens.
6. Record issues, owners, severity, and regression coverage for continued improvement.

## A practical example

A benefits application starts with semantic HTML and plain language, supports keyboard completion and 400% zoom, provides visible labels and useful errors, and is tested with screen readers and disabled participants before release and after major changes.

## Where it breaks

Accessibility standards are essential baselines but do not guarantee a usable or inclusive experience. Automated tools find only some barriers, conformance scope can be misunderstood, and access needs can conflict; human judgment and user research remain necessary.

## Common mistakes

- Treating accessibility as a final audit.
- Equating an automated scan with an accessible product.
- Designing for one assistive technology or one disability.
- Assuming a compliant component stays accessible in every context.

## Visualization

[View the visualization on the website](<https://wiki.soroush.uk/topic/accessibility/#visualization-accessibility>)

## Sources

1. [Introduction to Web Accessibility](<https://www.w3.org/WAI/fundamentals/accessibility-intro/>) — W3C Web Accessibility Initiative · Institutional guidance
2. [WCAG 2 Overview](<https://www.w3.org/WAI/standards-guidelines/wcag/>) — W3C Web Accessibility Initiative · Standards overview
3. [Making your service accessible: an introduction](<https://www.gov.uk/service-manual/helping-people-to-use-your-service/making-your-service-accessible-an-introduction>) — Government Digital Service · Government guidance

## Related topics

- [Inclusive Design](<https://wiki.soroush.uk/topic/inclusive-design/>)
- [WCAG](<https://wiki.soroush.uk/topic/wcag/>)
- [Usability Testing](<https://wiki.soroush.uk/topic/usability-testing/>)
