In short
- Definition: The degree to which a system can be used by people with the widest range of abilities, including users with visual, auditory, motor or cognitive impairments.
- Goal: Ensure that everyone, including people relying on assistive technologies, can perceive, operate and understand the system.
- Example S.M.A.R.T. requirement: 100% of criteria met on all key pages before each release.
1. Definition
As a non-functional requirement, accessibility describes how well people with the widest range of abilities can use a system: people who are blind or have low vision, who are deaf, who cannot use a mouse, or who have cognitive or learning disabilities [1], [2].
If a requirement says only “the site must be accessible”, nobody can test it. Name the standard, the level and the pages.Key takeaway
Accessibility also helps people in temporary or situational limits: a broken arm, bright sunlight on a phone screen, a noisy train. In ISO/IEC 25010:2023 it sits under interaction capability, as the sub-characteristic called inclusivity [3].
For websites and apps, the reference is the Web Content Accessibility Guidelines (WCAG) published by the W3C [4], [5]. Version 2.2 is the current Recommendation, and level AA is the target most laws and procurement rules point to.
2. Goal
The goal is that no user is excluded from the service because of a disability or of the device and assistive technology they rely on, such as a screen reader, voice control or a switch.
Forgetting accessibility is costly twice: it shuts out a large share of users, and it exposes the organization to complaints and legal action. Retrofitting it after launch usually means redesigning components, forms and color schemes that could have been right from the start.
3. How to Measure It (S.M.A.R.T.)
| Metric | Unit | Typical target | How to measure |
|---|---|---|---|
| WCAG 2.2 AA conformance | % of success criteria met | 100% on key user journeys | Manual audit by an accessibility specialist against the WCAG checklist |
| Automated accessibility errors | Errors per page | 0 critical errors | Automated scanner in the CI pipeline (e.g., axe-core, Lighthouse) |
| Assistive technology task success | % of tasks completed | ≥ 90% | Usability test with screen reader and keyboard-only users |
| Accessibility defects open | Count | 0 blocking defects at release | Defect tracker, label “accessibility” |
Automated tools catch only part of the problems. Always combine them with a manual review and with tests by real users of assistive technologies.
4. Example Requirements
Each requirement below is ready to copy into a specification: specific, measurable, achievable, relevant and time-bound.
- Public website: “Before go-live, all pages of the online application form shall conform to WCAG 2.2 level AA, as confirmed by an independent audit with no open blocking issue.”
- Internal tool: “Every release of the HR portal shall pass an automated accessibility scan with zero critical errors, and every new screen shall be operable with the keyboard alone.”
- Mobile app: “Within 3 months of launch, at least 90% of test users relying on VoiceOver or TalkBack shall complete the main purchase flow without help.”
5. Questions to Ask Stakeholders
- Which laws, policies or contracts set an accessibility level for this system?
- Which user groups and assistive technologies must be supported?
- Which journeys are critical and must be fully accessible first?
- Will documents (PDF, video, e-mail) also need to be accessible?
- Who will test with real users of assistive technologies, and when?
- How will accessibility be checked in every release, not only once?
6. Common Pitfalls
- Relying only on automated scanners. They miss problems such as unclear labels or illogical focus order. Add manual and user testing.
- Treating accessibility as a final check. Late fixes are expensive. Build it into design systems, components and acceptance criteria.
- Forgetting content. An accessible template filled with images without text alternatives, or videos without captions, is still inaccessible.
7. Related NFRs
- Categories of Non-Functional Requirements — the full checklist of NFR categories.
- Usability — an accessible system is usable by more people; many accessibility fixes improve usability for everyone.
- Compliance — accessibility is often a legal obligation for public bodies and many companies.
- Readability — clear, simple text is part of cognitive accessibility.
- Platform Compatibility — assistive technologies differ by platform and browser, so both must be tested together.
8. FAQ
Level AA is the usual target: it is the level referenced by most accessibility laws and policies. Level AAA is rarely required for a whole site.
No. Automated scanners find many issues quickly, but conformance needs a manual review and, ideally, tests with users of assistive technologies.
No. Captions, good contrast and keyboard support also help people in noisy places, in bright light or with a temporary injury.
9. Acronyms, Initialisms & Terms
Acronyms are abbreviations pronounced as words (like NASA); initialisms are spelled out letter by letter (like FBI). The classification below follows common pronunciation.
Acronyms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| ISO | International Organization for Standardization | Independent international body that publishes standards, such as ISO/IEC 25010 for software quality. Its short name comes from the Greek “isos” (equal) and is said as a word. | [6] |
| SMART | Specific, Measurable, Achievable, Relevant, Time-bound | Criteria for writing a goal or requirement so that anyone can check whether it has been met. | [7] |
| WCAG | Web Content Accessibility Guidelines | W3C standard that defines how to make web content accessible to people with disabilities. | [8] |
Initialisms
| Abbreviation | Stands for | Definition | Ref. |
|---|---|---|---|
| CI | Continuous integration | Practice of merging code changes often, with each change checked automatically by builds and tests. | [9] |
| FAQ | Frequently asked questions | List of common questions with their answers. | [10] |
| HR | Human resources | The department that manages employees, hiring and pay. | [11] |
| IEC | International Electrotechnical Commission | International standards body for electrical and electronic technologies; it publishes joint “ISO/IEC” standards with ISO. | [12] |
| NFR | Non-functional requirement | Requirement that describes how well a system must work (its qualities, such as speed or security) rather than what it does. | [2] |
| Portable Document Format | File format that keeps a document’s layout identical on any device. | [13] | |
| W3C | World Wide Web Consortium | International body that develops web standards, including HTML and WCAG. | [14] |
Terms
Plain-language definitions of technical and project-management terms used in this article.
| Term | Plain-language definition | Ref. |
|---|---|---|
| Pipeline (CI/CD) | Automated sequence of steps that builds, tests and deploys each code change. | [15] |
| Procurement | Process of selecting and buying goods or services from suppliers. | [16] |
| Requirement | Conditions a deliverable must meet to be accepted. | [17] |
| Screen reader | Software that reads screen content aloud for blind or low-vision users. | [18] |
| Stakeholder | Person or group with an interest in the system: users, sponsors, operators, regulators. | [19] |
| Usability testing | Observing real users as they try to complete tasks with a product. | [20] |
10. Sources and Further Reading
- [1] “Accessibility.” Wikipedia. https://en.wikipedia.org/wiki/Accessibility (accessed Nov. 18, 2026).
- [2] “Non-functional requirement.” Wikipedia. https://en.wikipedia.org/wiki/Non-functional_requirement (accessed Nov. 18, 2026).
- [3] “ISO/IEC 25010 product quality model.” ISO 25000. https://iso25000.com/index.php/en/iso-25000-standards/iso-25010 (accessed Nov. 18, 2026).
- [4] “Web Content Accessibility Guidelines (WCAG) 2.2.” W3C. https://www.w3.org/TR/WCAG22/ (accessed Nov. 18, 2026).
- [5] “What’s New in WCAG 2.2.” W3C. https://www.w3.org/WAI/standards-guidelines/wcag/new-in-22/ (accessed Nov. 18, 2026).
- [6] “International Organization for Standardization.” Wikipedia. https://en.wikipedia.org/wiki/International_Organization_for_Standardization (accessed Nov. 19, 2026).
- [7] “SMART criteria.” Wikipedia. https://en.wikipedia.org/wiki/SMART_criteria (accessed Nov. 19, 2026).
- [8] “Web Content Accessibility Guidelines.” Wikipedia. https://en.wikipedia.org/wiki/Web_Content_Accessibility_Guidelines (accessed Nov. 19, 2026).
- [9] “Continuous integration.” Wikipedia. https://en.wikipedia.org/wiki/Continuous_integration (accessed Nov. 19, 2026).
- [10] “FAQ.” Wikipedia. https://en.wikipedia.org/wiki/FAQ (accessed Nov. 19, 2026).
- [11] “Human resources.” Wikipedia. https://en.wikipedia.org/wiki/Human_resources (accessed Nov. 19, 2026).
- [12] “International Electrotechnical Commission.” Wikipedia. https://en.wikipedia.org/wiki/International_Electrotechnical_Commission (accessed Nov. 19, 2026).
- [13] “PDF.” Wikipedia. https://en.wikipedia.org/wiki/PDF (accessed Nov. 19, 2026).
- [14] “World Wide Web Consortium.” Wikipedia. https://en.wikipedia.org/wiki/World_Wide_Web_Consortium (accessed Nov. 19, 2026).
- [15] “CI/CD.” Wikipedia. https://en.wikipedia.org/wiki/CI/CD (accessed Nov. 19, 2026).
- [16] “Procurement.” Wikipedia. https://en.wikipedia.org/wiki/Procurement (accessed Nov. 19, 2026).
- [17] “Acceptance testing.” Wikipedia. https://en.wikipedia.org/wiki/Acceptance_testing (accessed Nov. 19, 2026).
- [18] “Screen reader.” Wikipedia. https://en.wikipedia.org/wiki/Screen_reader (accessed Nov. 19, 2026).
- [19] “Project stakeholder.” Wikipedia. https://en.wikipedia.org/wiki/Project_stakeholder (accessed Nov. 19, 2026).
- [20] “Usability testing.” Wikipedia. https://en.wikipedia.org/wiki/Usability_testing (accessed Nov. 19, 2026).
Written by Philippe Huard · LinkedIn · Last updated: November 18, 2026 · Header photo by @cdc; inline photo by @jimluo, both on Unsplash.








