Chapter 1: Understanding web accessibility
The chapter introduction frames accessibility as making digital technology usable for more people by accounting for changing abilities and removing barriers to everyday tasks.
After this chapter you will be able to
- Accessibility for changing abilities. Explain that digital accessibility aims to make technology usable by as many people as possible, not only people with disabilities, because people’s abilities and circumstances can change.
- Digital barriers and sound engineering. Describe how inaccessible design gets in the way of users’ tasks and why accessibility should be part of ordinary engineering rather than an add-on.
- Inclusive web app use. Explain what it means for a web app to be accessible across different abilities, contexts, and technologies.
- Accessibility as engineering baseline. Explain why the section treats accessibility as a baseline part of web engineering rather than an enhancement added afterward.
- Shared accessibility responsibility. Explain why accessibility is a core part of product development rather than a final QA or compliance task, and describe how different team roles influence it.
- Accessibility throughout the project lifecycle. Trace how accessibility requirements affect the appointment-booking example from requirements and design through development, testing, and post-release work.
- Broad value of accessibility. Explain why web accessibility matters beyond accommodating a small group of people or a few edge cases.
- Aging and accessibility needs. Explain why accessibility becomes more important as the population ages and how designing for older adults can improve interfaces for everyone.
- Broader appeal through accessibility. Explain why an accessible web app may attract more users and benefit existing ones.
- Location-dependent accessibility requirements. Explain why accessibility may be mandatory for a web app depending on where its users are, using the EU and US requirements named in the section. Distinguish the US federal-government scope of Section 508 from the broader US reference to the ADA.
- Semantic HTML and maintainability. Explain why highly accessible pages are typically easier to maintain and extend, and describe how semantic HTML contributes to their understandable structure.
- Accessibility and search visibility. Explain that making a website accessible to assistive technologies helps search engine crawlers understand its content and structure, which can improve SEO.
- Accessible structure for AI. Explain how accessible content and code help AI systems understand and interact with web apps, and why reducing ambiguity matters when those systems perform tasks for people.
- Inclusive design and engineering. Explain why accessibility is both a value for a web app’s growth strategy and a sign of solid engineering, using curb cuts as the example of a design choice that benefits people beyond its original users.
- WCAG and accessibility laws. Explain that WCAG is an international technical standard that many accessibility laws adopt, derive from, or use in practice, even when they do not name it explicitly.
- Checking applicable legal requirements. Describe why a web app team should check accessibility requirements in the regions where its app will be used, and how to start that check.
- WCAG’s role and status. Explain what WCAG is, what digital content it applies to, and how it relates to law.
- Principles criteria and conformance levels. Describe how WCAG organizes guidelines and uses success criteria to establish cumulative conformance levels.
- Four accessibility principles. Describe what Perceivable, Operable, Understandable, and Robust mean, using an example of the accessibility need each addresses.
- WCAG requirements hierarchy. Explain how principles, guidelines, and success criteria fit together, and distinguish required success criteria from informative implementation guidance.
- Cumulative conformance levels. Distinguish levels A, AA, and AAA, including what a Level AA target requires and why Level AAA is not generally a whole-site target.
- Content-dependent WCAG scope. Explain how a site’s content and functionality determine which WCAG guidelines and success criteria apply, and how adding content can change that scope.
- Ongoing conformance checks. Explain why conformance must be checked again as a website and its technology change.
- Content inventory for scoping. Describe how to use a manual or AI-assisted content inventory to identify potentially applicable WCAG success criteria, while distinguishing scoping from a conformance audit.
- Choosing a WCAG version. Explain why a project should generally refer to the most recent published WCAG version while also checking which version applies under the laws where the web app will be used.
- Human needs beyond conformance. Explain why accessibility work should prioritize user barriers rather than memorizing one WCAG version or treating conformance as sufficient by itself.
- User-centered guideline structure. Describe how WCAG 3 guidelines are expected to address documented user needs through requirements and outcomes, assertions, and technology-specific methods.
- Expected tiered conformance model. Distinguish WCAG 2.2's binary assessment of success criteria from WCAG 3's proposed tiered conformance model, including what Bronze, Silver, and Gold signify.
Section by section
Introduction
The chapter introduction frames accessibility as making digital technology usable for more people by accounting for changing abilities and removing barriers to everyday tasks.
- Accessibility for changing abilities: Explain that digital accessibility aims to make technology usable by as many people as possible, not only people with disabilities, because people’s abilities and circumstances can change.
Why it matters: This wider view helps you design for real people in the changing conditions of everyday life. - Digital barriers and sound engineering: Describe how inaccessible design gets in the way of users’ tasks and why accessibility should be part of ordinary engineering rather than an add-on.
Why it matters: Recognizing less-visible barriers helps teams build products people can actually use to get things done.
Key terms: digital accessibility, permanent, temporary, or situational limitations, barriers, sound engineering
1.1 What is web accessibility?
This section defines web accessibility as web apps that work for people with different abilities, contexts, and technologies, and presents it as a normal part of sound engineering.
- Inclusive web app use: Explain what it means for a web app to be accessible across different abilities, contexts, and technologies.
Why it matters: This definition keeps accessibility focused on whether people can actually use the app. - Accessibility as engineering baseline: Explain why the section treats accessibility as a baseline part of web engineering rather than an enhancement added afterward.
Why it matters: Treating accessibility as normal engineering changes it from an afterthought into an expected quality of the app. - Accessible engineering foundations and practices: Describe the technical foundation the section gives for accessible web apps and representative practices it includes.
Why it matters: These examples make the section's definition concrete for people building web apps.
Key terms: web accessibility, ability, context, assistive technologies, people-first design, solid engineering practices, baseline expectation, global technical debt, semantic HTML, accessibility guidelines
1.2 Where does accessibility fit in web projects?
Accessibility belongs in everyday product work across the whole lifecycle, with shared team responsibility and a technical foundation that supports broader design goals.
- Shared accessibility responsibility: Explain why accessibility is a core part of product development rather than a final QA or compliance task, and describe how different team roles influence it.
Why it matters: Treating accessibility as shared work helps teams build usable products from the start. - Accessibility throughout the project lifecycle: Trace how accessibility requirements affect the appointment-booking example from requirements and design through development, testing, and post-release work.
Why it matters: The booking example shows how an early requirement becomes ongoing design, implementation, testing, and maintenance work. - Cost of delayed accessibility: Explain how postponing accessibility creates technical debt and makes later fixes more difficult.
Why it matters: An apparent shortcut now can spread inaccessible patterns and increase the cost of fixing them later. - Accessible universal and inclusive design: Distinguish web accessibility, universal design, and inclusive design as the section defines them.
Why it matters: These distinctions clarify the difference between being able to use an app and having an experience designed for a broad, diverse audience.
Key terms: shared responsibility, product lifecycle, quality assurance, accessibility requirements, user journey, CI/CD, remediation, CMS, technical debt, inaccessible patterns
1.3 Why does accessibility matter?
This section frames accessibility as a broad product-quality concern rather than a fix for a few edge cases.
- Broad value of accessibility: Explain why web accessibility matters beyond accommodating a small group of people or a few edge cases.
Why it matters: Thinking of accessibility as product quality keeps it from being treated as an edge-case fix.
Key terms: web accessibility, usable, ethical, legally sound, technically stronger
1.3.1 The future relies on accessibility
Explains why an aging population makes web accessibility increasingly important and how designing for older adults benefits everyone.
- Aging and accessibility needs: Explain why accessibility becomes more important as the population ages and how designing for older adults can improve interfaces for everyone.
Why it matters: Accessibility addresses needs that become more common with age while improving the experience for a wider range of users.
Key terms: accessibility, older adults, visual, motor, auditory, or cognitive impairments
1.3.2 Get more people to love you
This section explains how accessibility can broaden a web app’s audience while benefiting existing users.
- Broader appeal through accessibility: Explain why an accessible web app may attract more users and benefit existing ones.
Why it matters: Accessibility can help more people use and appreciate what you build.
Key terms: accessible web app, content and functionality
1.3.3 Regulatory requirements
Accessibility can be a legal requirement depending on where users live, and compliance can reduce legal and reputational risk.
- Location-dependent accessibility requirements: Explain why accessibility may be mandatory for a web app depending on where its users are, using the EU and US requirements named in the section. Distinguish the US federal-government scope of Section 508 from the broader US reference to the ADA.
Why it matters: Legal requirements can make accessibility a necessary part of delivering a web app, not just a design preference.
Key terms: EN 301 549, Web Accessibility Directive, European Accessibility Act, Americans with Disabilities Act (ADA), Section 508, compliant
1.3.4 Maintainable code
This section connects maintainable web pages to clear structure and semantic HTML.
- Semantic HTML and maintainability: Explain why highly accessible pages are typically easier to maintain and extend, and describe how semantic HTML contributes to their understandable structure.
Why it matters: Choosing meaningful HTML elements helps other developers understand and change a page.
Key terms: semantic HTML, semantically correct HTML
1.3.5 Improved Search Engine Optimization
This subsection explains why accessibility can improve search engine optimization.
- Accessibility and search visibility: Explain that making a website accessible to assistive technologies helps search engine crawlers understand its content and structure, which can improve SEO.
Why it matters: Accessibility can help people use your site while also making it easier for search engines to interpret.
Key terms: assistive technologies, screen readers, search engine crawlers, SEO scores, Semantic HTML
1.3.6 More effective AI systems and agents
Accessible content and code help AI systems interpret and operate web apps more reliably, especially when acting on people’s behalf.
- Accessible structure for AI: Explain how accessible content and code help AI systems understand and interact with web apps, and why reducing ambiguity matters when those systems perform tasks for people.
Why it matters: Clear, accessible web apps are less likely to lead AI systems astray when people use them to complete important tasks.
Key terms: semantic markup, clear structure, predictable relationships, understandable content, task-oriented agents
1.3.7 More inclusivity through rigorous engineering
The section argues that accessibility makes web apps more inclusive while demonstrating thoughtful engineering that can benefit many people.
- Inclusive design and engineering: Explain why accessibility is both a value for a web app’s growth strategy and a sign of solid engineering, using curb cuts as the example of a design choice that benefits people beyond its original users.
Why it matters: Accessibility can be both an inclusive choice and a mark of thoughtful product engineering.
Key terms: accessibility, inclusive, growth strategy, curb cuts, solid engineering capabilities
1.4 Are there any laws that I need to be aware of?
This section explains how accessibility standards and human rights commitments shape laws around the world, and how to identify the requirements that may apply to a web app.
- WCAG and accessibility laws: Explain that WCAG is an international technical standard that many accessibility laws adopt, derive from, or use in practice, even when they do not name it explicitly.
Why it matters: Knowing WCAG’s role helps you understand why it matters across different legal systems without assuming every law cites it. - Standards becoming local requirements: Trace how WCAG can become part of regional and local requirements using the EU example.
Why it matters: This example shows why an international technical standard can matter to a product’s local legal obligations. - Human rights treaty influence: Explain how the UN Convention on the Rights of Persons with Disabilities connects equal digital access to local accessibility measures.
Why it matters: Accessibility requirements are shaped not only by technical standards but also by a commitment to equal access. - Checking applicable legal requirements: Describe why a web app team should check accessibility requirements in the regions where its app will be used, and how to start that check.
Why it matters: Checking the rules for a product’s actual markets helps a team avoid treating accessibility as optional or relying on outdated general guidance.
Key terms: WCAG, W3C, ADA, Section 508, EN 301 549, Web Accessibility Directive, European Accessibility Act, United Nations Convention on the Rights of Persons with Disa, CRPD, ICT
1.5 WCAG – a bird’s eye view
This section introduces WCAG as a global accessibility standard, outlines how its criteria support conformance claims, and explains how recent versions have expanded its scope.
- WCAG’s role and status: Explain what WCAG is, what digital content it applies to, and how it relates to law.
Why it matters: This distinction helps you understand why WCAG is widely used without mistaking it for legislation. - Principles criteria and conformance levels: Describe how WCAG organizes guidelines and uses success criteria to establish cumulative conformance levels.
Why it matters: This structure explains what a claimed WCAG conformance level represents. - Evolution of WCAG versions: Trace the broad changes described from WCAG 2.0 through 2.2.
Why it matters: The changes show how WCAG has responded to technologies and barriers that earlier versions addressed less fully.
Key terms: WCAG, technical standard, digital accessibility, POUR, success criteria, conformance, Level A, Level AA, Level AAA, WCAG 2.0
1.5.1 How does WCAG work?
This section explains how WCAG organizes accessibility goals into principles, guidelines, and testable success criteria, and how its conformance levels and informative resources help teams apply them.
- Four accessibility principles: Describe what Perceivable, Operable, Understandable, and Robust mean, using an example of the accessibility need each addresses.
Why it matters: POUR gives you a way to reason about barriers from the user's perspective. - WCAG requirements hierarchy: Explain how principles, guidelines, and success criteria fit together, and distinguish required success criteria from informative implementation guidance.
Why it matters: This distinction tells you what you must satisfy and where you have flexibility in implementation. - Cumulative conformance levels: Distinguish levels A, AA, and AAA, including what a Level AA target requires and why Level AAA is not generally a whole-site target.
Why it matters: A conformance target only makes sense if you know which criteria it includes and what its limits are. - Informative technique categories: Distinguish sufficient techniques, advisory techniques, and common failures, and describe how a technique's test procedure can help assess a criterion.
Why it matters: These resources help you choose and check an approach without mistaking guidance for a requirement. - WCAG interpretation resources: Describe what Understanding documents, ACT rules, supplemental guidance, and the Quick Reference help a team do.
Why it matters: Knowing which resource to consult helps you interpret a requirement or investigate a difficult test case.
Key terms: POUR, Perceivable, Operable, Understandable, Robust, principles, guidelines, success criteria, normative, informative
1.5.2 What does WCAG conformance mean?
Explains that WCAG conformance depends on a site’s current content, requires reassessment as the site changes, and can be scoped with a content inventory.
- Content-dependent WCAG scope: Explain how a site’s content and functionality determine which WCAG guidelines and success criteria apply, and how adding content can change that scope.
Why it matters: You can focus WCAG checks on what your site actually contains without overlooking criteria that become relevant later. - Ongoing conformance checks: Explain why conformance must be checked again as a website and its technology change.
Why it matters: A site that conformed before an update may need fresh checks afterward. - Content inventory for scoping: Describe how to use a manual or AI-assisted content inventory to identify potentially applicable WCAG success criteria, while distinguishing scoping from a conformance audit.
Why it matters: An inventory gives you a practical starting scope without mistaking an automated list for proof of conformance.
Key terms: conformance, guidelines, success criteria, out of scope, accessibility concerns, content inventory, scoping exercise, conformance audit, rendered DOM
1.5.3 Which WCAG version should I use?
This section explains how to choose a WCAG version while keeping accessibility grounded in people’s needs rather than a single version’s rules.
- Choosing a WCAG version: Explain why a project should generally refer to the most recent published WCAG version while also checking which version applies under the laws where the web app will be used.
Why it matters: The newest published guidance is a useful starting point, but a project also needs to account for applicable law. - Human needs beyond conformance: Explain why accessibility work should prioritize user barriers rather than memorizing one WCAG version or treating conformance as sufficient by itself.
Why it matters: A focus on people’s barriers remains useful even when guidelines and interfaces change.
Key terms: W3C Recommendation, WCAG 2.2, WCAG 3, human needs, user challenges, conformance, barriers
1.5.4 Looking ahead to WCAG 3
This section describes the expected shift from WCAG 2.2 to WCAG 3 while emphasizing that reducing accessibility barriers remains the goal.
- User-centered guideline structure: Describe how WCAG 3 guidelines are expected to address documented user needs through requirements and outcomes, assertions, and technology-specific methods.
Why it matters: This explains what the proposed guidelines are meant to focus on, beyond simply passing tests. - Expected tiered conformance model: Distinguish WCAG 2.2's binary assessment of success criteria from WCAG 3's proposed tiered conformance model, including what Bronze, Silver, and Gold signify.
Why it matters: It captures the proposed change in how conformance would be expressed. - Continuity and remaining uncertainty: Explain why existing WCAG 2.2 Level A and AA work is expected to carry over substantially, while noting that WCAG 3 may require additional work and its exact scoring is unsettled.
Why it matters: It prevents treating either today's conformance or WCAG 3's proposed scoring as a settled guarantee.
Key terms: guidelines, documented user needs, requirements and outcomes, assertions, methods, success criteria, conformance model, Bronze, Silver, Gold
1.6 The journey towards building an accessible web app
This section outlines the topics the book will cover on the journey toward building an accessible web app.
1.7 Summary
1.8 References
This section lists three sources cited in the chapter.
Where this is used later
- Meet your users (chapter 2) · Frames consideration of users whose needs and circumstances differ.
- Assistive technologies (chapter 2) · Explores technologies some users rely on.
- The fundamental rule: semantic HTML reigns supreme (chapter 2) · Develops the section's introductory point about semantic HTML.
- Build keyboard-friendly websites (chapter 5) · Develops keyboard access and focus behavior.
- Handle errors and help users recover effectively (chapter 6) · Develops support for recovering from errors.
- Keep it POSH (Plain Old Semantic HTML) (chapter 2) · Provides the reason to favor plain semantic HTML.
- Ensure sufficient contrast (chapter 3) · Applies the Perceivable principle to visual contrast.
- Forms done right (chapter 6) · Applies understandable interaction to forms and errors.
Concepts explained in this chapter
- WCAGWCAG 2.1 is the 2018 edition of the Web Content Accessibility Guidelines, adding requirements for mobile accessibility, low vision, and cognitive disabilities.
- accessibilityDigital accessibility is the design of digital products and services so that people with disabilities can perceive, operate, understand, and interact with them.
- conformanceAccessibility conformance is the degree to which a product or content satisfies applicable accessibility requirements.
- WCAG guidelineA WCAG guideline is an accessibility goal organized under one of WCAG’s principles and supported by testable success criteria.
- WCAG success criterionA WCAG success criterion is a testable requirement for meeting a WCAG guideline at a specified conformance level.
- POUR principlesThe POUR principles are WCAG’s four organizing principles: perceivable, operable, understandable, and robust.
- Level AAWCAG 2.2 Level AA is a conformance target comprising the Level A and Level AA requirements of WCAG version 2.2.
- WCAG conformance levelA conformance level is a graded classification indicating which set of an accessibility standard’s requirements has been met.
- advisory techniqueAn advisory technique is an optional implementation approach that improves accessibility beyond the minimum needed for conformance.
- common failureA common failure is a recurring implementation pattern that causes content to fail a particular WCAG success criterion.
- sufficient techniqueA sufficient technique is a documented implementation approach that can satisfy a particular WCAG success criterion in a stated situation.
- semantic markupSemantic HTML is the use of HTML elements whose names and structure convey the meaning, role, and organization of content.
- ACT ruleAn ACT rule is a technology-specific procedure for testing an individual accessibility success criterion, especially in automated testing or auditing.
- informative contentInformative content is explanatory specification material that provides examples, techniques, and interpretation without imposing conformance obligations.
- keyboard interfaceA keyboard interface is an interaction mechanism through which content functionality can be operated using keyboard input.
- supplemental guidanceSupplemental guidance is optional WCAG-related guidance for addressing accessibility barriers beyond the formal conformance requirements.
- understanding documentAn understanding document is WCAG supporting documentation that explains the intent, terms, beneficiaries, examples, techniques, and failures of a guideline or success criterion.
- accessibility APIAn accessibility API is a platform interface through which applications expose user-interface structure, meaning, state, and functionality to assistive technologies.
- accessibility requirementAn accessibility requirement is a product or system requirement specifying accessibility obligations or capabilities that the system must satisfy.
- accessible web applicationAn accessible web application is a web application designed so that people with diverse abilities, devices, input methods, and viewing conditions can use it.
- ISO 9241An international standard series covering human-computer interaction and ergonomics.
- automated accessibility checkAn automated accessibility check is a software-based test that detects potential accessibility violations in digital content or interfaces.
- inclusive designA human-centered design approach that accommodates diverse abilities, identities, backgrounds, and circumstances while fostering a sense of belonging.
- technical debtTechnical debt is the accumulated future cost created by choosing incomplete, inferior, or deferred technical solutions.
- universal designA design approach that aims for one product or environment to work well for the widest possible range of people without separate alternatives.
- user experienceUser experience is a person's overall perceptions and responses resulting from interacting with a product or system.
- EN 301 549EN 301 549 V4.1.0 is a specific version of the European standard for accessibility requirements for information and communication technology products and services.
- WCAG 3.0WCAG 3 is a draft successor to the Web Content Accessibility Guidelines that proposes an outcome-focused accessibility conformance model.
- Americans with Disabilities ActThe Americans with Disabilities Act is a United States civil-rights law prohibiting discrimination against people with disabilities, including in covered goods and services.
- Section 508Section 508 is a United States federal accessibility requirement for information and communication technology procured, developed, maintained, or used by federal agencies.
- accessibility barrierAn accessibility barrier is a feature, condition, or design decision that prevents or impedes people from accessing or using technology.
- JavaScriptJavaScript is a programming language standardized as ECMAScript and commonly used to add behavior and interaction to web pages and applications.
- WAI-ARIAARIA is a W3C standard for adding accessibility semantics and interaction-state information to web content and user interface widgets.
- keyboard focusA focus state is the visual or programmatic state indicating which interactive element currently receives keyboard input.
- accessible authenticationAccessible authentication is an authentication process designed so that people with disabilities can complete it without unnecessary barriers.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.
