WCAG 3.0 Key Concepts and Terminology
A reference guide to the new vocabulary and conceptual framework that underpins WCAG 3.0. Understand guidelines, requirements, methods, assertions, functional needs, and outcomes.
How WCAG 3.0 Concepts Connect
The relationship between the core building blocks of the WCAG 3.0 framework.
Concept Deep Dive
Each of the six core concepts explained in detail, with WCAG 2.x comparisons and practical examples.
Guidelines
Definition
Outcome statements that describe what accessible content should achieve. Rather than abstract organizational groupings, WCAG 3.0 guidelines are actionable outcome descriptions.
WCAG 2.x Equivalent
"Guidelines" existed in WCAG 2.x but were more abstract organizational groupings under the four POUR principles (Perceivable, Operable, Understandable, Robust).
Example
"Users can perceive all non-decorative images through text alternatives" is a WCAG 3.0 guideline outcome — specific, measurable, and user-centered.
Key Insight
Guidelines in WCAG 3.0 are organized into 12 functional categories rather than 4 principles, providing more granular and practical groupings.
Requirements
Definition
WCAG 3 has three types of provisions: core requirements, which must all be met to conform; supplemental requirements, which build on the core set and are not required to conform; and assertions, which are documented statements about accessibility practices an organization follows.
WCAG 2.x Equivalent
"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.
Example
A core requirement might be: "All non-decorative images have a text alternative that describes the image’s purpose."
Key Insight
These are provision types, not levels. Conformance depends only on the core requirements; supplemental requirements and assertions feed the separate reporting tiers.
Methods
Definition
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.
WCAG 2.x Equivalent
"Techniques" in WCAG 2.x were informative and advisory. WCAG 3.0 ties methods more tightly to conformance: the methods you rely on must be accessibility supported.
Example
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.
Key Insight
A method only counts toward conformance if browsers and assistive technologies in general use actually support it. WCAG 3 calls this being accessibility supported, and the accessibility support set must be stated in a conformance claim.
Assertions
Definition
Documented organizational commitments requiring evidence. Organizations publicly state what they provide for accessibility and back it up with documentation, training records, and process descriptions.
WCAG 2.x Equivalent
No equivalent exists in WCAG 2.x — this is an entirely new concept introduced in WCAG 3.0.
Example
"We provide accessibility training to all developers" with evidence: training records, certificates, and curriculum documentation.
Key Insight
Assertions acknowledge that real accessibility requires organizational commitment — not just technical fixes. Culture, process, and policy matter.
Functional Needs
Definition
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.
WCAG 2.x Equivalent
Partially relates to "Understanding" documents, but WCAG 2.x was organized by technical principles (POUR), not user needs.
Example
"Users who cannot see need text alternatives for visual content" describes a functional need that drives multiple guidelines and requirements.
Key Insight
Centering on functional needs rather than disability categories is more inclusive and technology-resilient — it future-proofs the standard.
Reporting Tiers
Definition
Six cumulative tiers that describe how far a product has got, each one building on the tiers below it: 1 avoid physical harm, 2 foundational access, 3 conformance, 4 Bronze, 5 Silver, 6 Gold. Conformance itself is tier 3, where every core requirement is met.
WCAG 2.x Equivalent
Closest to WCAG 2.x conformance levels (A / AA / AAA), but the September 2026 draft deliberately separates the two ideas. As the editors put it, WCAG 3 “moves the concept of leveling from conformance to reporting”, and uses the phrase “reporting tiers” to keep them distinct from the old “conformance levels”.
Example
A product that meets every core requirement has conformed, and reports at tier 3. Reaching tier 5 (Silver) additionally requires a number of supplemental requirements and assertions about content.
Key Insight
Conformance is a single bar, not a ladder. The tiers exist to report progress toward it and achievements beyond it. This section is still marked exploratory, and the Working Group is openly asking whether tiers or a scoring model works better.
Terminology Mapping: WCAG 2.x to 3.0
A quick reference for how familiar WCAG 2.x terms translate to the new WCAG 3.0 vocabulary.
How It All Fits Together
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.
Explore More WCAG 3.0 Guides
Continue learning about WCAG 3.0 with our detailed companion guides.
WCAG 3.0 Overview
The complete overview of WCAG 3.0 and its significance for web accessibility.
Read overview12 Guideline Categories
Deep dive into the 12 functional categories that replace the POUR principles.
Read guideWCAG 3.0 vs WCAG 2.2
Side-by-side comparison of the two standards and the new conformance model.
Read comparisonHow to Prepare
Actionable steps your team can take today to get ready for WCAG 3.0.
Read preparation guideEssential Accessibility Resources
Comprehensive tools, checklists, and guides to help you create inclusive digital experiences