Accessibility
Digital accessibility means designing and developing products so people with disabilities can perceive, understand, navigate, interact, and contribute.
Download Markdown (.md)Soroush’s Product Wiki · https://wiki.soroush.uk/topic/accessibility/
01What 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.[1][2][3]
- Perceivable
- Information available through usable sensory alternatives
- Operable
- Controls work across keyboard, pointer, voice, and assistive input
- Understandable
- Language, navigation, behavior, and errors remain clear
- Robust
- Semantics interoperate with browsers and assistive technology
- Context
- Disability, environment, device, language, and temporary constraints
- Participation
- Disabled people influence research, design, testing, and governance
Accessibility is a continuing design and engineering responsibility, not a final compliance check or a feature only for a small separate audience.
02Why 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.
03When 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.
04How it works
- Include disabled people and relevant access needs in research and decision-making.
- Use semantic structures, clear content, flexible presentation, and multiple input methods.
- Apply appropriate standards and platform guidance as testable baselines.
- Test early with keyboards, zoom, settings, automated tools, and assistive technologies.
- Test complete tasks with disabled participants, not only individual screens.
- Record issues, owners, severity, and regression coverage for continued improvement.
05A 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.
06Where 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.
07Sources
- Introduction to Web AccessibilityW3C Web Accessibility Initiative · Institutional guidanceIntroduction to Web Accessibility
- WCAG 2 OverviewW3C Web Accessibility Initiative · Standards overviewWCAG 2 Overview
- Making your service accessible: an introductionGovernment Digital Service · Government guidanceMaking your service accessible: an introduction