A page that works for one person may create a barrier for someone who sees, hears, or controls it differently. A WCAG guideline names an accessibility goal for a broad range of needs, including permanent, temporary, and situational ones. It is organized under one of four principles: perceivable, operable, understandable, or robust. section 1.5.1
In WCAG 2.2, each of the 13 guidelines has testable success criteria. These criteria—not the supporting examples or techniques—are the requirements used to determine conformance. They have levels A, AA, and AAA; each higher level includes the requirements of the levels below it. section 1.5 section 1.5.1
From goal to implementation
Suppose a page’s headings are hard to identify. An HTML technique listed by WCAG is to use h1–h6 elements to identify headings. Treat the technique as implementation help, then check the relevant success criteria to establish what conformance requires. The WCAG Quick Reference lets you filter guidelines, criteria, techniques, and failures for the technology you use. section 1.5.1
TIP: Start with the barrier a person faces, then use the guideline to find relevant criteria and guidance. Do not mistake an informative technique for a required implementation. WCAG focuses on user needs rather than a particular web framework. section 1.5.1
NOTE: WCAG 3 is expected to give guidelines a different structure, with requirements, assertions, and technology-specific methods. Its conformance model is still being developed; WCAG 2.2’s testable success criteria remain the described basis for current conformance. section 1.5.4
