Overview

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.
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.
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.
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.
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.
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.

FAQ

What is web accessibility?Web accessibility is the practice of designing and building web applications so that people can perceive, understand, and use content and functionality regardless of ability, context, or the technology they use.
Who benefits from web accessibility?Everyone benefits from web accessibility, not just people with permanent disabilities. Accessibility also helps users with temporary or situational limitations, such as a broken arm, noisy environment, bright sunlight, or using a phone on a bumpy bus.
Why is accessibility considered foundational rather than optional?Accessibility is foundational because digital products are now central to communication, work, and entertainment. If people cannot use a product effectively, the product falls short of its purpose.
Where should accessibility be considered in a web project?Accessibility should be considered from day one and throughout the entire product lifecycle, including requirements, design, development, QA, content updates, support, and maintenance.
What are the four core principles of WCAG?The four core WCAG principles are Perceivable, Operable, Understandable, and Robust, often abbreviated as POUR.
What do WCAG success criteria represent?WCAG success criteria are specific, testable requirements that define what must be met to claim conformance. They are the normative core of WCAG and function like acceptance criteria for accessibility.
What do WCAG conformance levels A, AA, and AAA mean?Level A is the minimum level of accessibility, Level AA adds stronger accessibility requirements and is the most commonly targeted level, and Level AAA is the highest level but is rarely required for entire websites.
Why does accessibility matter for business and user experience?Accessibility helps products reach more people, improves usability for everyone, supports SEO, strengthens maintainability, reduces legal risk, and can improve the overall perception of the brand.
How do laws and standards relate to web accessibility?Many accessibility laws around the world are based on or reference WCAG. Standards such as EN 301 549, Section 508, and various regional laws use WCAG as a technical foundation for compliance.
What is the difference between accessibility, universal design, and inclusive design?Accessibility is the technical foundation that ensures people with different abilities can use a product. Universal design aims to make one solution work well for as many users as possible, while inclusive design goes further by considering broader human diversity such as culture, race, gender, age, language, and location.

pro $24.99 per month

  • access to all Manning books, MEAPs, liveVideos, liveProjects, and audiobooks!
  • choose one free eBook per month to keep
  • exclusive 50% discount on all purchases
  • renews monthly, pause or cancel renewal anytime

lite $19.99 per month

  • access to all Manning books, including MEAPs!

team

5, 10 or 20 seats+ for your team - learn more


Close
choose your plan

team

monthly
annual
$49.99
$499.99
only $41.67 per month
  • five seats for your team
  • access to all Manning books, MEAPs, liveVideos, liveProjects, and audiobooks!
  • choose another free product every time you renew
  • choose twelve free products per year
  • exclusive 50% discount on all purchases
  • renews monthly, pause or cancel renewal anytime
  • renews annually, pause or cancel renewal anytime
  • Architecting Accessibility Architecting Accessibility ebook for free
Close
choose your plan

team

monthly
annual
$49.99
$499.99
only $41.67 per month
  • five seats for your team
  • access to all Manning books, MEAPs, liveVideos, liveProjects, and audiobooks!
  • choose another free product every time you renew
  • choose twelve free products per year
  • exclusive 50% discount on all purchases
  • renews monthly, pause or cancel renewal anytime
  • renews annually, pause or cancel renewal anytime
  • Architecting Accessibility Architecting Accessibility ebook for free