Loading...
A reference guide to the new vocabulary and conceptual framework that underpins WCAG 3.0. Understand guidelines, requirements, methods, assertions, functional needs, and outcomes.
The relationship between the core building blocks of the WCAG 3.0 framework.
Each of the six core concepts explained in detail, with WCAG 2.x comparisons and practical examples.
Outcome statements that describe what accessible content should achieve. Rather than abstract organizational groupings, WCAG 3.0 guidelines are actionable outcome descriptions.
"Guidelines" existed in WCAG 2.x but were more abstract organizational groupings under the four POUR principles (Perceivable, Operable, Understandable, Robust).
"Users can perceive all non-decorative images through text alternatives" is a WCAG 3.0 guideline outcome — specific, measurable, and user-centered.
Guidelines in WCAG 3.0 are organized into 12 functional categories rather than 4 principles, providing more granular and practical groupings.
Testable provisions that come in three types: core requirements (mandatory for conformance), supplemental requirements (additional support beyond core), and assertions (organizational commitments requiring documentation).
"Success Criteria" in WCAG 2.x served a similar role, but WCAG 3.0 requirements are more granular and introduce assertions as an entirely new type.
A core requirement might be: "All non-decorative images have a text alternative that describes the image’s purpose."
The three-tier structure (core / supplemental / assertions) allows more nuanced conformance than WCAG 2.x’s binary pass/fail model.
Technology-specific approaches for meeting requirements, with detailed test procedures and expected results. Methods tell you exactly how to test a given requirement for a specific technology.
"Techniques" in WCAG 2.x were informative and advisory. WCAG 3.0 methods are normative, with specific test procedures that must be followed.
An HTML method for image alternatives might include: check for the alt attribute, verify it describes the image purpose, and ensure decorative images use an empty alt.
Methods are normative (not just informative) and include specific test procedures, making testing more consistent across auditors and organizations.
Documented organizational commitments requiring evidence. Organizations publicly state what they provide for accessibility and back it up with documentation, training records, and process descriptions.
No equivalent exists in WCAG 2.x — this is an entirely new concept introduced in WCAG 3.0.
"We provide accessibility training to all developers" with evidence: training records, certificates, and curriculum documentation.
Assertions acknowledge that real accessibility requires organizational commitment — not just technical fixes. Culture, process, and policy matter.
User-need-based groupings that drive the entire framework. They describe what users need to successfully use content, regardless of specific disability categories or medical diagnoses.
Partially relates to "Understanding" documents, but WCAG 2.x was organized by technical principles (POUR), not user needs.
"Users who cannot see need text alternatives for visual content" describes a functional need that drives multiple guidelines and requirements.
Centering on functional needs rather than disability categories is more inclusive and technology-resilient — it future-proofs the standard.
Measurable results that guidelines aim to achieve, representing the conceptual shift from "conformance" to demonstrating real user impact. Outcomes measure degree of achievement rather than binary pass/fail.
The overall concept of "conformance" but measured differently — WCAG 2.x was binary (pass or fail), while WCAG 3.0 measures the degree of achievement on a graduated scale.
Rather than "alt text exists" (pass/fail), an outcome measures "users can understand the purpose of images" with graduated scoring.
Outcomes-based assessment provides more meaningful measurement of real-world accessibility impact than checkbox compliance.
A quick reference for how familiar WCAG 2.x terms translate to the new WCAG 3.0 vocabulary.
A worked example tracing image alt text through the entire WCAG 3.0 framework, from user need to organizational commitment.
Users who cannot see need text alternatives for visual content.
Non-decorative images have meaningful text alternatives.
All informative images have an accessible name describing their purpose.
HTML: Check img elements have alt attributes with descriptive text.
Organization documents its alt text authoring process and QA review.
Continue learning about WCAG 3.0 with our detailed companion guides.
The complete overview of WCAG 3.0 and its significance for web accessibility.
Read overviewDeep dive into the 12 functional categories that replace the POUR principles.
Read guideSide-by-side comparison of the two standards and the new conformance model.
Read comparisonActionable steps your team can take today to get ready for WCAG 3.0.
Read preparation guideComprehensive tools, checklists, and guides to help you create inclusive digital experiences