liveBook · Manning

Chapter 1: Understanding web accessibility

What you will learn in chapter 1 of Architecting 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

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.

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.

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.

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.

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.

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.

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.

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.

Key terms: semantic HTML, semantically correct HTML

1.3.5 Improved Search Engine Optimization

This subsection explains why accessibility can improve search engine optimization.

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.

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.

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.

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.

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.

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.

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.

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.

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

Concepts explained in this chapter

Chapter 2: People, technologies, and fundamental techniques →

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.