WCAG 3.0: What Changes from Previous Versions and How to Prepare Now

WCAG 3.0 isn’t just another version update — it’s a model change. Here’s what it introduces, how it differs from WCAG 2.1 and 2.2, and the steps you can take now without waiting for the final spec.

WCAG 3.0: a model change, not just a version bump

WCAG 2.x set the web accessibility standard for over a decade with a binary model: each criterion either passes or fails. WCAG 3.0 breaks from that logic and proposes a graduated scoring system, a broader requirements structure, and a scope that extends well beyond static web content.

Understanding what changes — and when — is essential for organizations that manage digital systems under legal accessibility obligations.

Where we stand: WCAG 2.2 as the current baseline

WCAG 2.2, published in October 2023, is the current stable version. It added nine new success criteria, including requirements on focus visibility, minimum target size for interactive elements, and authentication that doesn’t depend on cognitive functions.

In the U.S., Section 508 currently references WCAG 2.0 Level AA as the baseline for federal agencies, while the EU Accessibility Act — which took effect in June 2025 for most digital services — references WCAG 2.1 AA. Updating to WCAG 2.2 isn’t yet mandated in most frameworks, but organizations auditing and improving today should work against 2.2 to avoid technical debt going into the next transition.

What WCAG 3.0 introduces

WCAG 3.0 — officially W3C Accessibility Guidelines 3.0, in draft since 2021 — is not an incremental update. It’s a rewrite of the model.

A new conformance system

The model shifts from binary (pass / fail) to graduated. Outcomes are scored on a scale of 0 to 4, and conformance is classified into three levels: bronze, silver, and gold. Bronze is the minimum entry point and is roughly equivalent to WCAG 2.x Level AA.

A new requirements structure

WCAG 3.0 drops the four POUR principles (Perceivable, Operable, Understandable, Robust) and replaces them with guidelines grouped by outcomes. Each guideline defines a functional goal for the user — not a technical property of the content.

Broader scope

The standard extends its coverage to more disability types — especially cognitive disabilities and low vision — and accounts for a wider range of usage contexts: native apps, augmented reality, moving content, and conversational interfaces.

More testable criteria

One recognized problem with WCAG 2.x is ambiguity in the interpretation of some criteria. WCAG 3.0 moves toward more precise and repeatable evaluation methods, with test protocols defined per outcome.

When it takes effect

WCAG 3.0 is still in active draft. The W3C has not set an official publication date as a recommendation. The most conservative estimate points to no earlier than 2026–2027, and regulatory adoption in legal frameworks — the EU Accessibility Act, Section 508 updates, and national equivalents — will take additional years.

That doesn’t mean ignoring it. Organizations that start understanding the model now will have a significant advantage when the transition becomes mandatory.

How to prepare without waiting for the final version

Audit against WCAG 2.2 AA today

Preparing for WCAG 3.0 starts with consolidating conformance with WCAG 2.2. Organizations with unresolved 2.1 debt are not in a position to anticipate 3.0.

Understand the graduated scoring model

The most disruptive change is conceptual: moving from “we comply / we don’t comply” to “what level of experience are we delivering to users with disabilities?” Introducing quality-of-experience metrics — not just technical conformance checks — prepares teams to operate within that framework.

Build in cognitive accessibility criteria now

WCAG 3.0 places significantly more weight on cognitive accessibility. Plain language, predictable navigation, reduced cognitive load, and accessible authentication are areas where you can make real progress today, regardless of which version of the standard applies.

Document and measure

WCAG 3.0 penalizes the absence of evidence. Systems with audit processes, documented evaluated criteria, and recorded improvement plans will be much better positioned to demonstrate conformance under the new model.

Follow the W3C process

W3C drafts are published at w3.org/TR/wcag-3.0/. Tracking updates — or delegating that to a specialized team — allows you to anticipate changes before they become enforceable.

The time to act is now

WCAG 3.0 is not urgent from a regulatory standpoint. Strategically, it is. Organizations that wait for the legal mandate arrive late — with more technical debt and less room for an orderly transition.

Auditing, documenting, and improving against WCAG 2.2 today is the most direct path to being ready for what’s coming.

Frequently Asked Questions

Does WCAG 3.0 replace WCAG 2.2?

Not in the near term. WCAG 2.2 is the current stable standard. WCAG 3.0 is still in draft and its regulatory adoption will take years. Organizations should focus on WCAG 2.2 now and start building conceptual familiarity with the transition.

When will WCAG 3.0 become mandatory?

There is no official date. The W3C estimates the final version won't arrive before 2026–2027, and its adoption into regulatory frameworks — including the EU Accessibility Act and federal standards like Section 508 — will take additional time.

What happens to systems that already comply with WCAG 2.1 AA?

They meet current legal requirements in most jurisdictions. However, WCAG 2.2 adds relevant criteria and WCAG 3.0 changes the entire conformance model. Auditing against 2.2 today is the most cost-effective step toward preparing for the transition.

What do the bronze, silver, and gold levels mean in WCAG 3.0?

These are the three conformance levels in the new graduated model. Bronze is the minimum entry point and is roughly equivalent to WCAG 2.x Level AA. Silver and gold require greater coverage, more rigorous evaluation methods, and documented evidence. Most organizations will target bronze in the first phase of the transition.

Does WCAG 3.0 only apply to websites, or also to mobile apps and other environments?

WCAG 3.0's scope is broader than previous versions. It covers native applications, conversational interfaces, augmented reality, and moving content — not just web pages. This is especially relevant for organizations with mobile apps or mixed digital channels subject to accessibility obligations.