1 Understanding web accessibility
The chapter introduces web accessibility as a fundamental part of building digital products, not a special feature for a small group. It explains that accessibility helps people in many different situations, such as using a phone in bright sunlight, navigating with a keyboard, or relying on captions in a noisy environment. In this view, accessible technology adapts to human variability instead of forcing users to adapt to the product.
It then frames accessibility as a core engineering responsibility that should be considered from the start of a project and shared across roles. Designers, developers, product owners, QA, content teams, and support all influence whether a product can be used effectively, efficiently, and satisfactorily. The chapter emphasizes that ignoring accessibility creates technical debt, increases remediation cost, and can make products functionally incomplete, while early attention improves usability, inclusivity, maintainability, and even search visibility.
Finally, the chapter gives a practical overview of the standards and laws that shape accessibility work, especially WCAG. It explains the four POUR principles, the role of testable success criteria, and the difference between conformance levels and supporting techniques. The chapter also notes that accessibility requirements vary by region but are often grounded in international standards, and it closes by outlining the broader journey ahead: understanding the standards, choosing the right technologies, designing inclusive experiences, and sustaining accessibility over time.
Accessibility affects nearly every aspect of software development, from planning and design to post-launch content management and support. Everyone has a responsibility to ensure users can actually access content and functionality.
This image illustrates the various components in WCAG 2.2. Guidelines are organized under four principles. Each of the 13 guidelines includes normative success criteria: the requirements used to determine conformance at levels A, AA, or AAA. WCAG also provides informative supporting material, including techniques, understanding documents, testing rules, and additional guidance to help explain and apply those requirements.
The four principles underpinning WCAG 2.2 – and the associated guidelines and success criteria – ensure that technology is accessible to the widest range of people, regardless of differences in ability, whether permanent, temporary, or situational. Content and functionality must be perceivable through different senses, operable in different ways, understandable and predictable, and robust across a wide range of technologies, including assistive technologies.
Distribution of WCAG 2.2 success criteria across conformance levels (A, AA, AAA). This highlights the relative size and complexity of higher conformance levels.
The stages of building accessible web applications: understanding accessibility standards and regulations, determining core web technologies for accessible content and functionality, designing inclusive security, addressing modern web-app challenges, and sustaining accessibility over time.
Summary
- Accessibility is not just for people with disabilities – it improves usability and experience for everyone.
- Accessibility is not another step in your QA processes; it reflects core engineering competence and responsible product development and management. It belongs at the heart of your process, not at the end.
- Accessibility matters for societal, commercial, legal, and technical reasons – it’s the right thing to do, and doing it well means you’re building things the right way.
- In many jurisdictions around the world, accessibility is not optional – it is a legal requirement.
- Most accessibility laws worldwide reference or align with the W3C’s Accessibility Guidelines (WCAG), the globally recognized standard for digital accessibility. WCAG is created through a rigorous, collaborative process involving hundreds of contributors from industry, government, academia, and accessibility communities, with the goal of providing a single, widely accepted set of guidelines.
- WCAG 2.2 is organized around 4 principles, which are broken down into 13 guidelines. Each guideline includes a set of testable success criteria (normative), defined at three conformance levels: A, AA, and AAA. WCAG also provides additional informative documentation to help interpret and meet the success criteria, including sufficient and advisory techniques, as well as common failures.
- Accessibility conformance is not a one-and-done activity – but an ongoing process. Embedding it into your workflow helps ensure quality, reduce risk, and keep your product future-proof.
Architecting Accessibility ebook for free