frameworkExperience & interface

WCAG

WCAG is the W3C’s testable international standard for making web content more accessible to people with disabilities.

Download Markdown (.md)

01What it means

The Web Content Accessibility Guidelines organize accessibility under four principles: perceivable, operable, understandable, and robust. WCAG 2.2 contains normative success criteria at levels A, AA, and AAA, supported by non-normative understanding documents and techniques.[1][2][3]

02Why it matters

WCAG provides a shared vocabulary and testable baseline for teams, evaluators, organizations, and policy contexts. It helps convert many accessibility needs into acceptance criteria and regression checks, while supporting consistent reporting of findings.

03When to use it

Use WCAG to define and evaluate the accessibility of web content, including during requirements, design review, development, procurement, and audits. Choose the version, conformance target, technologies, and evaluation scope explicitly.

04How it works

  1. Read the normative principles, guidelines, success criteria, and conformance requirements.
  2. Map relevant criteria to designs and implementation acceptance tests.
  3. Use understanding documents to study intent, benefits, examples, and edge cases.
  4. Combine automated checks with structured manual testing and assistive technology use.
  5. Evaluate complete pages and processes within the declared scope.
  6. Report failures by criterion, evidence, user impact, location, and remediation priority.

05A practical example

Example

A team targeting WCAG 2.2 Level AA maps form designs to labels, errors, focus, reflow, contrast, target size, and authentication criteria. It tests a complete account-opening process and records reproducible evidence rather than attaching a generic accessibility score.

06Where it breaks

WCAG is not a design method, usability guarantee, or substitute for research with disabled people. Some criteria require interpretation, AAA is not appropriate as a blanket target for all content, and passing isolated checks does not prove an end-to-end task is usable.

Common mistakes

  • Reading techniques as the only permitted implementations.
  • Reporting a single score without criterion-level evidence.
  • Testing only the home page or component catalog.
  • Making legal conclusions from WCAG results without jurisdiction-specific expertise.

07Sources

  1. Web Content Accessibility Guidelines (WCAG) 2.2World Wide Web Consortium · StandardWeb Content Accessibility Guidelines (WCAG) 2.2
  2. WCAG 2 OverviewW3C Web Accessibility Initiative · Standards overviewWCAG 2 Overview
  3. Introduction to Web AccessibilityW3C Web Accessibility Initiative · Institutional guidanceIntroduction to Web Accessibility
View saved topics

Start typing to search titles, definitions, categories, and frameworks.