WCAG 2.2 vs WCAG 3.0: What's Coming and When

WCAG 3.0 — formally known as the W3C Accessibility Guidelines — is the most significant restructuring of web accessibility standards since WCAG 2.0 launched in 2008. It is still in working draft status as of mid-2026, with no firm recommendation date set. But its design choices are already clear enough to understand what compliance will look like when it arrives.

This article covers what WCAG 3.0 actually changes, how it differs from 2.2, and what you can do now to prepare without disrupting your current obligations.

Where Things Stand Today

WCAG 2.2 (October 2023) is the current W3C Recommendation and the baseline referenced by most accessibility laws globally — including the EU’s EN 301 549, the European Accessibility Act, and the UK’s public sector regulations. It is what you must comply with today.

WCAG 3.0 is a Working Group Note in active development by the Accessibility Guidelines Working Group (AG WG). It has gone through multiple public working drafts. The group has explicitly stated it will not reach Recommendation status in the near term — 2027 is the earliest realistic timeline, and further slippage is likely given the scope of the redesign.

There will be no cliff-edge switch. When WCAG 3.0 does become a standard, regulators will give transition periods — just as they did when countries moved from WCAG 2.0 to 2.1.

The Core Structural Change: From Criteria to Outcomes

The most fundamental difference is philosophical.

WCAG 2.x is structured around Success Criteria — specific, testable, pass/fail rules. “Color contrast must be at least 4.5:1.” Either it is, or it isn’t. This binary structure made automated testing straightforward but created problems: meeting every criterion does not guarantee a usable experience, and many real-world barriers are hard to reduce to a single measurable test.

WCAG 3.0 shifts to Outcomes — higher-level statements of what the user experience must achieve — with multiple test methods supporting each outcome. A test can be:

Atomic — a specific measurable check (similar to current success criteria)
Holistic — requires user testing or expert evaluation across a complete flow

This means WCAG 3.0 conformance will involve a mix of automated checks and qualitative evaluation, not just a checklist.

The New Conformance Model: Bronze, Silver, Gold

WCAG 2.x uses three conformance levels: A, AA, AAA. Most legal standards require AA.

WCAG 3.0 replaces this with a tiered model based on the proportion and quality of outcomes met:

Level	What It Means
Bronze	All critical outcomes pass; no widespread failures across any outcome
Silver	Bronze requirements met, plus advancements in additional outcomes
Gold	Silver requirements met, with documented user research and continuous improvement processes

Bronze is expected to be the legal minimum — roughly equivalent to today’s AA. Silver and Gold reward organisations that go further, including ongoing testing with disabled users and formal accessibility maturity programmes.

Importantly, Bronze is not easy. The bar for “no widespread failures” is higher than simply passing every automated scan.

APCA: A New Approach to Colour Contrast

One of the most discussed technical changes in WCAG 3.0 is the replacement of the current contrast algorithm (WCAG 2.x uses a relative luminance ratio) with APCA — the Advanced Perceptual Contrast Algorithm.

The current ratio (4.5:1 for normal text, 3:1 for large text) is a blunt instrument. It does not account for how the human visual system actually perceives contrast across different font weights, sizes, and polarities (light-on-dark vs dark-on-light).

APCA calculates a Lightness Contrast (Lc) value and applies different thresholds based on font size and weight. A 16px bold text has a different minimum Lc than a 12px regular text, and dark-on-light is scored differently from light-on-dark.

Practical implication: Some colour combinations that currently fail WCAG 2.x contrast will pass under APCA, and vice versa. Organisations using APCA-compliant design systems now are building a head start — but there is no urgency to abandon WCAG 2.x contrast compliance today.

Broader Scope: Beyond Websites

WCAG 2.x was written for web content. WCAG 3.0 is explicitly designed to apply to:

Native mobile applications (iOS, Android)
Virtual and augmented reality interfaces
Immersive 3D environments
Emerging interaction paradigms (voice-first, gesture-driven, AI-assisted)

This means the outcomes and test methods include scenarios that simply do not exist in WCAG 2.x, addressing how accessibility is tested when there is no traditional web DOM.

Functional Categories Instead of POUR

WCAG 2.x organises success criteria around four principles: Perceivable, Operable, Understandable, Robust (POUR). Designers and developers have internalised this structure over 15+ years.

WCAG 3.0 replaces POUR with functional user needs as the organising principle. Outcomes are grouped by what they enable users to accomplish — reading, navigating, interacting, understanding — rather than by the technical nature of the barrier.

The working drafts are still settling on the exact category structure, so this may continue to evolve.

What Is NOT Changing

Despite the structural overhaul, the underlying accessibility knowledge does not change:

The same types of barriers (missing alt text, poor contrast, inaccessible forms, keyboard traps) remain barriers
Automated testing still plays a central role — atomic tests in WCAG 3.0 map closely to existing axe-core and WAVE rules
The need for manual expert review and user testing with disabled people grows, not shrinks
The POUR principles remain a useful mental model even if the official taxonomy changes

Organisations that build genuine accessibility competence now will have no difficulty mapping their practices to WCAG 3.0 when it arrives.

What to Do Now

Continue pursuing WCAG 2.2 AA compliance. It is the current legal standard in every major jurisdiction and the foundation on which WCAG 3.0 Bronze will be built. There is no scenario where being WCAG 2.2 AA compliant is a disadvantage when WCAG 3.0 arrives.

Start integrating user testing with disabled people. Silver and Gold levels will require documented evidence of testing with real users. Beginning that practice now builds organisational muscle and produces better products — regardless of what the final WCAG 3.0 spec says.

Follow the working drafts. The AG WG publishes updates at w3.org/TR/wcag-3.0/. Major decisions about the conformance model, APCA thresholds, and functional categories are still being made. If you have products that will be long-lived, assign someone to monitor developments.

Do not wait for WCAG 3.0 to fix known issues. Known barriers are costing you users and increasing your legal exposure today. There is no compliance benefit to delaying remediation.

WCAG 3.0 will eventually arrive and it will require a shift in how accessibility is measured and demonstrated. But it will not make WCAG 2.2 compliance irrelevant — it will build on it. The organisations best positioned for the transition are the ones building real accessibility programmes now, not the ones waiting for the final standard.