WCAG 3.0: The Next Generation of Accessibility Standards
The W3C Accessibility Guidelines (WCAG) 3.0 represents a fundamental reimagining of accessibility standards. With 12 guideline categories, six reporting tiers in place of A/AA/AAA, and scope beyond web content — here is everything you need to know.
What Changed in the 10 September 2026 Working Draft
This draft supersedes the one published on 3 March 2026. These are the substantive changes.
Leveling moved out of conformance
A new Reporting section now carries the idea of levels. The editors write that WCAG 3 “moves the concept of leveling from conformance to reporting”, and use the term “reporting tiers” to keep it distinct from the old “conformance levels”. The previous draft’s Conformance level subsection is gone.
Six reporting tiers, with Bronze, Silver, and Gold above conformance
The tiers are cumulative: 1 avoid physical harm, 2 foundational access, 3 conformance, 4 Bronze, 5 Silver, 6 Gold. Conformance is tier 3, reached when every core requirement is met. Tiers 4 to 6 add supplemental requirements and assertions, and the exact numbers are still marked TBD.
Core requirements are tagged by severity
Every core requirement now carries one of four tags describing the worst-case impact of failing it: Physical Harm, Risk, Barrier, or Friction. These tags are what build the reporting tiers. Assertions are separately tagged as being about Content or about the Organization.
Conformance advanced from exploratory to developing
The Conformance section changed maturity status between the two 2026 drafts. The new Reporting section is still marked exploratory.
Best practices renamed Recommended Practices
They remain informative and are not needed to conform, but they are now named consistently and can take the form of either a provision or a method.
Images and media split into nine guidelines
The old Media alternatives guideline was dissolved. Transcripts, Sign language, and Accessible media player are now guidelines in their own right, and Figure captions moved up to 2.1.2. Transcripts, captions, and audio descriptions each gained a full set of requirements covering speakers, sounds, visual information, style guides, and usability testing.
Text appearance gained minimum and enhanced requirements
Blocks of text readable, text style readable, and text contrast sufficient each now appear in both a minimum and an enhanced form, alongside the existing adjustability requirements.
Requirement type moved from headings into tags
Headings used to read “Core requirement: Images detectable”. They now read “Images detectable”, with the type carried as a tag. Some requirements were also renamed, including No flashing to No flashing over threshold, and No repetitive links to No repetitive adjacent interactive elements.
The tier model is not settled
An editor’s note in the Reporting section records an alternative proposal that would use scoring to show progress toward conformance and then award Bronze, Silver, and Gold after it. The Working Group is inviting public comment on which approach to take, so treat the six tiers as the current direction rather than a decided outcome.
Source: W3C Accessibility Guidelines (WCAG) 3.0, W3C Working Draft 10 September 2026
The Evolution of Accessibility Standards
WCAG 3.0 builds on over two decades of web accessibility guidelines.
What Makes WCAG 3.0 Different
New Name, Broader Scope
Renamed from "Web Content Accessibility Guidelines" to "W3C Accessibility Guidelines", reflecting expanded scope covering web, native apps, authoring tools, user agents, IoT devices, and virtual/augmented reality.
Reporting Tiers, Not Levels
No more A/AA/AAA. Conformance is one bar: meet every core requirement. Six cumulative reporting tiers then describe where you are, from avoiding physical harm up through Bronze, Silver, and Gold.
12 Guideline Categories
The 4 POUR principles (Perceivable, Operable, Understandable, Robust) evolve into 12 functional categories — from Images & Media to Policy & Protection — covering new areas like cognitive accessibility and algorithmic fairness.
Explore WCAG 3.0 In Depth
Dive deeper into specific aspects of WCAG 3.0 with our detailed guides.
12 Guideline Categories
WCAG 3.0 vs WCAG 2.2
Key Concepts & Terminology
How to Prepare
WCAG 3.0 Conceptual Framework
How the new building blocks of WCAG 3.0 connect to form a cohesive accessibility framework.
Guidelines
Outcome statements that describe what accessible content should achieve, organized into 12 functional categories.
Requirements
Testable provisions in two kinds: core requirements, which must all be met to conform, and supplemental requirements, which go beyond conformance.
Methods
Technology-specific approaches for meeting a requirement or assertion. A method only counts toward conformance if it is accessibility supported.
Assertions
Documented statements about accessibility practices an organization follows — tagged as being about content or about the organization.
Reporting tiers
Six cumulative tiers that replace conformance levels, running from avoiding physical harm through conformance to Bronze, Silver, and Gold.
Functional Needs
User-need-based groupings that drive the entire framework, replacing disability-category approaches with functional descriptions.
Important: WCAG 3.0 Is Not Final
- Working Draft status — the specification is subject to significant changes and is not ready for implementation requirements.
- Does not deprecate WCAG 2.x — WCAG 2.2 remains the current, stable standard for compliance and legal purposes.
- Legal requirements unchanged — ADA, Section 508, EN 301 549, and the European Accessibility Act continue to reference WCAG 2.x.
- Several years remaining — the W3C Working Group has confirmed substantial work is still needed before the final Recommendation.
Frequently Asked Questions
When will WCAG 3.0 be finalized?
The most recent Working Draft was published on 10 September 2026. The W3C Accessibility Guidelines Working Group states that while the draft has moved closer toward completion, it still has several years of work remaining. There is no firm date for the final Recommendation, but organizations should monitor progress and begin familiarizing themselves with the new framework now.
Does WCAG 3.0 replace WCAG 2.2?
No, WCAG 3.0 does not deprecate WCAG 2.x. WCAG 2.2 remains the current, stable standard and will continue to be required by laws and regulations in many countries for the foreseeable future. WCAG 3.0 is being developed in parallel and will eventually provide an alternative path to conformance.
Should I start following WCAG 3.0 now?
Not yet for compliance purposes — WCAG 3.0 is still a Working Draft and subject to significant changes. However, understanding its direction is valuable. The best preparation is ensuring strong WCAG 2.2 AA compliance, as content meeting WCAG 2.2 is expected to satisfy most of WCAG 3.0's minimum conformance level.
What is the difference between WCAG 2 and WCAG 3?
WCAG 3.0 represents a fundamental redesign. It replaces the 4 POUR principles with 12 guideline categories, expands scope beyond web content to include apps, tools, and devices, and introduces new concepts like assertions and functional needs. The September 2026 draft also moves the idea of levels out of conformance entirely: conformance is a single bar (meet every core requirement), and progress toward and beyond that bar is expressed through six reporting tiers rather than A/AA/AAA.
Will WCAG 3.0 affect legal compliance requirements?
Not immediately. Current laws (ADA, Section 508, EN 301 549, EAA) reference WCAG 2.x. It will take years after WCAG 3.0 is finalized for regulatory bodies to update their requirements. Organizations should continue meeting WCAG 2.2 AA for legal compliance while monitoring WCAG 3.0 development.
Is WCAG 3.0 harder to meet than WCAG 2.2?
It is different rather than harder, but it is not a straight swap. The W3C states that content conforming to WCAG 2.2 Level A and Level AA is expected to meet most of the minimum conformance level of the new standard, so existing accessible content largely transfers. It also warns that WCAG 3 adds tests WCAG 2.2 does not have, so additional work will be needed to reach full conformance.
Essential Accessibility Resources
Comprehensive tools, checklists, and guides to help you create inclusive digital experiences