Skip to main content
Back to all posts

WCAG 3.0: What Developers Need to Know in 2026

Benjamin Morton

WCAG 3.0 has been "coming soon" for five and a half years. The first public draft landed in January 2021, and the ninth is dated 3 March 2026. It's still a Working Draft, which in W3C terms means unstable, incomplete, and liable to change again before anyone has to comply with it (W3C WCAG 3.0, 2026).

That gap between the hype and the status is where most write-ups go wrong. They describe a Bronze/Silver/Gold scoring system that the current draft has dropped, quote a "174 requirements" figure that belongs to an old draft, and leave developers thinking they should pause and re-plan around a standard that won't be finished this decade. So this post sticks to what the 3 March 2026 draft actually says, what genuinely changes, and what you should do about it today. The short version of that last part: nothing new.

TL;DR: WCAG 3.0 is still an early Working Draft (latest 3 March 2026, the ninth since 2021) and isn't expected to be a finished W3C standard before 2028, realistically 2029-2030 (W3C; AbilityNet). It will not deprecate WCAG 2.2, and a 2.2 AA site already meets most of 3.0's minimum conformance. Keep shipping against 2.2. The medal levels (Bronze/Silver/Gold) you may have read about were dropped from the current draft.

When Will WCAG 3.0 Actually Be Released?

Not for years. The latest Working Draft is dated 3 March 2026, the ninth since the first public draft in January 2021, and W3C's own guidance says WCAG 3 "is not expected to be a completed W3C standard for a few more years" (W3C WAI, 2026). "A few more years" is doing a lot of work in that sentence.

Five Versions in 24 Years. The Sixth Is Still a Draft. 1.0 1999 2.0 2008 2.1 2018 2.2 2023 3.0 2026 WD 3.0 2029? First draft January 2021. Ninth Working Draft March 2026. A finished standard is not expected before 2028, and reputable estimates put it closer to 2029-2030. The dashed segment is projected, not scheduled. Source: W3C publication history and WCAG 3 Introduction; AbilityNet; Deque (2026)

Put dates on it and the picture gets clearer. AbilityNet, tracking the working group's own plans, expects a Candidate Recommendation around Q4 2027 and a final Recommendation "not earlier than 2028" (AbilityNet, 2026). Deque, whose staff sit on the working group, put it more bluntly back in 2024: even optimistically it won't be finished before 2028, and "we may not see WCAG 3.0 before 2030" (Deque, 2024).

Treat those years as informed estimates, not a W3C-published schedule, because W3C hasn't committed to one. But the direction is unambiguous. WCAG 2.0 took nearly seven years from its first draft to Recommendation. WCAG 3.0 is more ambitious and started in 2021. Do the arithmetic and 2029 looks generous, not pessimistic.

Citation capsule: WCAG 3.0 remains a W3C Working Draft as of 3 March 2026, its ninth since January 2021 (W3C, 2026). W3C says it is "not expected to be a completed W3C standard for a few more years"; independent estimates from AbilityNet and Deque put the final Recommendation at 2028 at the earliest and more realistically 2029-2030. There is no committed W3C release date.

Is WCAG 2.2 Obsolete Now?

No. The draft states it plainly: "WCAG 3 is a successor to Web Content Accessibility Guidelines 2.2 but does not deprecate WCAG 2" (W3C WCAG 3.0, 2026). W3C goes further in its introduction, saying 2.x "will not be deprecated for at least several years after WCAG 3 is finalized" (W3C WAI, 2026).

Stack those two statements and you get a runway measured in years on top of years. WCAG 3.0 isn't finished until roughly 2029, and WCAG 2.2 stays valid for several years after that. On any reasonable reading, 2.2 is the standard developers build against well into the 2030s.

There's a practical reassurance underneath the timeline, too. Content that conforms to WCAG 2.2 Level A and AA "is expected to meet most of the minimum conformance level of this new standard" (W3C WCAG 3.0, 2026). In plain terms: the work you do to reach 2.2 AA isn't throwaway effort that 3.0 will invalidate. It's most of the way to 3.0's floor already. If you want the concrete list, our WCAG 2.2 compliance checklist is the version to work through now.

What Actually Changes in WCAG 3.0?

Almost everything structural. WCAG 3.0 replaces the pass/fail success criteria of 2.x with a layered model of guidelines, requirements, assertions and methods, and it drops the familiar A/AA/AAA levels for "several levels of conformance" (W3C WCAG 3.0, 2026). This is a rebuild of how conformance works, not a renumbering of the old rules.

Here's the shape of the new model against the one you know:

Dimension

WCAG 2.2

WCAG 3.0 (current draft)

Testable unit

Success criteria, pass or fail

Requirements, with methods and tests

Conformance levels

A / AA / AAA

"Several levels of conformance" (core plus supplemental)

Scoring

Binary: you meet it or you don't

A flexible, graded model

How-to guidance

Techniques

Methods (broader technology coverage)

Organisational commitments

None

Assertions

A couple of the labels moved even within the last draft. What earlier drafts called "outcomes" became "requirements" in March 2026, and "foundational requirements" became "core requirements" (W3C WAI, 2026). If terminology shifts between two consecutive drafts, that tells you how settled the rest of it is.

Now the two things everyone gets wrong, because they're worth getting right.

Bronze, Silver and Gold are gone. You'll read all over the web that WCAG 3.0 rates sites Bronze, Silver or Gold. That was a proposal in earlier drafts. The current 3 March 2026 draft doesn't use medal names at all; it refers only to generic "levels of conformance" built from core requirements, supplemental requirements and assertions (W3C WCAG 3.0, 2026). If a post is still selling you Bronze/Silver/Gold as current fact, it hasn't opened the draft recently.

The "174 requirements" number is out of date, too. That figure comes from the May 2024 draft, where the working group floated 174 candidate outcomes against the 78 success criteria in WCAG 2.1 (Deque, 2024). The current draft publishes no such total and explicitly excludes early-status material from any count. Quoting "174" as the size of WCAG 3.0 in 2026 is quoting a two-year-old snapshot of a moving target.

What WCAG 3.0 Tries to Fix That 2.2 Couldn't

It reaches well past the web page. The draft's scope covers web content plus mobile and native apps, authoring and testing tools, browsers and assistive technologies, and emerging tech like AR and VR (W3C WCAG 3.0, 2026). WCAG 2.x was written for web content and has been stretched to cover apps by analogy ever since. WCAG 3.0 aims to cover them by design.

What Each Standard Aims to Cover WCAG 2.2 (today) WCAG 3.0 (draft) Web content Web content Mobile & native apps Authoring & testing tools Browsers & assistive tech XR / AR / VR Wearables & IoT Blue is what WCAG 2.2 already covers. Amber is new territory in the 3.0 draft, none of it final. Source: W3C WCAG 3.0 Working Draft, 3 March 2026

The other genuine expansion is cognitive and learning disability. The draft aims to "cover more user needs, including more needs of people with cognitive disabilities", with concrete requirements like providing explanations or unambiguous alternatives for non-literal language such as idioms and metaphors (W3C WAI, 2026).

That's the part worth caring about, because it's where 2.x is genuinely weak. In the US, cognitive disability is the largest single category, affecting 13.9% of adults against 5.5% for vision, yet our review of the accessibility statistics found most tooling and most success criteria serve the smaller group. WCAG 2.x is thinnest exactly where the largest group of users needs it most. Whatever else WCAG 3.0 gets tangled up in, aiming at that gap is the right target.

So Should You Wait for WCAG 3.0?

No, and waiting has a cost. Every accessibility law on the books today points at WCAG 2.x, not 3.0. The European Accessibility Act works through EN 301 549, which references WCAG 2.1. US Section 508 references WCAG 2.0. And ADA case law sits behind the 3,117 federal website accessibility lawsuits filed in 2025, up 27% on the year (Seyfarth Shaw, 2026). Not one of them cites WCAG 3.0, because it doesn't exist as a standard yet.

So "let's wait for 3.0" is really "let's carry our current legal exposure for another four years and then scramble". The regulators won't switch the moment W3C publishes, either; adoption of a new reference standard into law lags the Recommendation by years, the way EN 301 549 still points at 2.1 rather than 2.2. There is no version of the timeline where waiting pays off. A WCAG 2.2 AA site is both what the law wants now and most of what 3.0 will want later. You'd be optimising for a deadline that is always receding while ignoring the ones that keep landing, like the ADA Title II deadline and live EAA enforcement.

There's a scanning angle here as well. WCAG 3.0's graded, flexible conformance model is, oddly, closer to how automated tools already behave than the strict pass/fail of 2.x is. A scanner that returns a 0-100 score, the way a11yFlow does, is already expressing something like a graded result rather than a single binary verdict. The move from "pass/fail" to "level" is less of a leap for tooling than it sounds. It doesn't change what you should measure today: 2.2 success criteria.

What Developers Should Do Today

Treat WCAG 2.2 AA as the standard and keep shipping against it. A site that already conforms to 2.2 AA "is expected to meet most of the minimum conformance level" of WCAG 3.0 (W3C WCAG 3.0, 2026), so the work carries forward rather than being wasted. Concretely:

  • Get to WCAG 2.2 AA and stay there. It's the de facto standard, the legal reference, and the foundation 3.0 builds on. Start from the compliance guide and work the 2.2 checklist.
  • Fix the high-volume failures first. Low-contrast text, missing labels and the rest of the usual suspects account for the overwhelming majority of real-world errors. Our guide to fixing common WCAG violations walks through them with code.
  • Watch the drafts, don't chase them. Read each new Working Draft for direction, but don't re-architect around an unstable spec. Anything you build to today's draft may not match next year's.
  • Pre-invest in one thing: cognitive accessibility. Plain language, predictable navigation, generous timeouts and clear error recovery are where 3.0 clearly heads, and they help real users right now. That's the rare bit of "future-proofing" that pays off before the standard even ships.

The honest summary is that WCAG 3.0 shouldn't change your 2026 roadmap at all. It should change how you talk about the far future, and nothing you build this quarter.

Frequently Asked Questions

When will WCAG 3.0 be finalised?

Not before 2028, and more realistically 2029-2030. As of July 2026 it's still a Working Draft (latest 3 March 2026), and W3C says it's "not expected to be a completed W3C standard for a few more years" (W3C, 2026). AbilityNet projects a Candidate Recommendation around Q4 2027. There is no committed W3C release date.

Does WCAG 3.0 replace WCAG 2.2?

No. The draft says WCAG 3 "does not deprecate WCAG 2", and W3C adds that 2.x won't be deprecated "for at least several years after WCAG 3 is finalized" (W3C, 2026). WCAG 2.2 stays the standard developers build against well into the 2030s, and current accessibility laws all reference WCAG 2.x.

Does WCAG 3.0 still use Bronze, Silver and Gold?

No. Medal levels were an earlier proposal. The current 3 March 2026 Working Draft dropped them for generic "levels of conformance" built from core requirements, supplemental requirements and assertions (W3C, 2026). Any source still describing Bronze/Silver/Gold as current is out of date.

Will my WCAG 2.2 AA site pass WCAG 3.0?

Largely, yes. W3C states that content conforming to WCAG 2.2 Level A and AA "is expected to meet most of the minimum conformance level" of WCAG 3.0 (W3C, 2026). The main gaps will be around cognitive accessibility and the broader scope, so 2.2 AA work is a strong foundation, not wasted effort.

Should I stop new accessibility work until 3.0 lands?

No. Every legal obligation today, the EAA via EN 301 549, US Section 508, ADA case law, references WCAG 2.x. Website accessibility lawsuits rose 27% to 3,117 in US federal courts in 2025 (Seyfarth Shaw, 2026). Waiting for 3.0 means carrying that exposure for years with nothing to show for it.

The Bottom Line

WCAG 3.0 is real, it's a genuine rethink, and it's years away. The latest Working Draft is dated March 2026, a finished standard isn't expected before 2028 and more likely lands around 2029-2030, and even then WCAG 2.2 stays valid for years afterwards (W3C, 2026). It rebuilds conformance around requirements, methods and assertions, drops the A/AA/AAA levels, and reaches past the web page into apps, tools and emerging tech, with a proper push on cognitive accessibility.

None of that should change what you do this year. The Bronze/Silver/Gold scoring you've read about is gone from the current draft, the "174 requirements" figure is two years stale, and the standard everyone will still be audited against for the foreseeable future is WCAG 2.2. Get to 2.2 AA, fix the common violations that cause most real failures, and read the drafts for direction rather than deadlines. The teams that quietly reach 2.2 AA now will find WCAG 3.0 was most of the way done for them.

Sources

PreviousARIA Mistakes Developers Make (and How to Fix Them)
NextColor Contrast WCAG 2.2: A Developer's Fix Guide (CSS)