Skip to main content
Back to all posts

WCAG 3.0 Release Date and What Changes

Benjamin Morton

As of October 2026, WCAG 3.0 has no release date. The latest version is the tenth Working Draft, dated 10 September 2026, and W3C says WCAG 3 "is not expected to be a completed W3C standard for a few more years" (W3C WCAG 3.0; W3C WAI, 2026). It has been "coming soon" since the first public draft in January 2021, and a Working Draft is, in W3C's own words, a "work in progress" that can still change before anyone has to comply with it.

That gap between the hype and the status is where most write-ups go wrong. They describe Bronze, Silver and Gold as the levels you'll have to hit, quote a "174 requirements" figure that belongs to a 2024 draft, and leave developers thinking they should pause and re-plan around a standard that won't be finished for years. The September 2026 draft rewrote conformance yet again, so this post sticks to what that 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 a Working Draft (the tenth, dated 10 September 2026) and W3C has set no release date. The working group's own schedule aims for a Candidate Recommendation in Q4 2027, so a finished standard isn't expected before 2028, realistically 2029-2030 (W3C; AGWG schedule; 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 September draft has one conformance level (meet every core requirement); Bronze, Silver and Gold survive only as proposed reporting tiers above it.

When Will WCAG 3.0 Actually Be Released?

Not for years. The latest Working Draft is dated 10 September 2026, the tenth since the first public draft in January 2021 (W3C publication history, 2026), 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.

Four Versions in 24 Years. The Fifth Is Still a Draft. 1.0 1999 2.0 2008 2.1 2018 2.2 2023 3.0 Sep 2026 10th draft 3.0 2029? First draft Jan 2021. Tenth Working Draft Sep 2026. Candidate Recommendation aimed for late 2027. Final standard not expected before 2028, more likely 2029-2030. The dashed part is projected. Sources: W3C history, WCAG 3 Introduction, AGWG schedule (2026); AbilityNet (2026); Deque (2024)

Put dates on it and the picture gets clearer. The working group's projected schedule, which W3C links from its WCAG 3 introduction, aims to publish WCAG 3 as a Candidate Recommendation Snapshot in Q4 2027, and notes that "historically, it has taken an additional 2 years from that point to final publication" (AGWG WCAG 3 schedule, 2026). AbilityNet reads the same plan as 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 plans and estimates, not a release date. W3C hasn't committed to one, the schedule page says it "does not necessarily represent consensus", and it has already slipped once this year: the Working Draft planned for April to June 2026 "slipped to the beginning of September" (AGWG WCAG 3 schedule, 2026). But the direction is unambiguous. WCAG 2.0 took nearly eight years from its first Working Draft in January 2001 to Recommendation in December 2008 (W3C WCAG 2.0 history). 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 October 2026. The latest is the tenth, dated 10 September 2026, since the first public draft in January 2021 (W3C, 2026). W3C says it is "not expected to be a completed W3C standard for a few more years". The working group's schedule targets a Candidate Recommendation Snapshot in Q4 2027, and 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 WCAG 2 "will not be deprecated for 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 success criteria of 2.x with a layered model of guidelines, requirements, assertions and methods, and it drops the familiar A/AA/AAA levels. In the September 2026 draft there is one conformance level: "all core requirements MUST be satisfied" (W3C WCAG 3.0, 2026). Progress below and above that line is reported in tiers instead. 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

Core and supplemental requirements, with methods and tests

Conformance levels

A / AA / AAA

One: meet every core requirement

Reporting progress

Binary: you meet it or you don't

Six proposed tiers, from "avoid physical harm" up to Gold (scoring is the alternative proposal)

How-to guidance

Techniques

Methods (broader technology coverage)

Organisational commitments

None

Assertions

The labels keep moving between drafts. The March 2026 draft had three conformance levels, Bronze, Silver and Gold, with Bronze as "the minimum level of conformance" (W3C, March 2026 draft, 2026). Six months later the September draft "moves the concept of leveling from conformance to reporting", and what March called "best practices" are now "recommended practices" (W3C WCAG 3.0, 2026). If the conformance model can change that much 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 no longer conformance levels. You'll read all over the web that WCAG 3.0 rates sites Bronze, Silver or Gold, with Bronze as the minimum. That was how the March 2026 draft worked. In the 10 September 2026 draft you conform by meeting every core requirement. Bronze, Silver and Gold appear only as reporting tiers 4 to 6, stacked above conformance and built from a still-undecided number of supplemental requirements and assertions. Below conformance, tier 1 covers requirements tagged "physical harm" and "risk", and tier 2 adds the "barrier" ones. An editor's note says the working group is also weighing an alternative that uses scoring to show progress and then awards Bronze, Silver and Gold after conformance (W3C WCAG 3.0, 2026). If a post still sells you Bronze as the floor you must reach, it hasn't opened the latest draft.

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 it leaves out every requirement and assertion still at Exploratory status. Quoting "174" as the size of WCAG 3.0 in 2026 is quoting a 2024 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, 10 September 2026

The other genuine expansion is cognitive and learning disability. W3C says WCAG 3 aims to "cover more user needs, including more needs of people with cognitive disabilities" (W3C WAI, 2026), and the draft has concrete provisions to match, such as a supplemental requirement that explanations or unambiguous alternatives are available for non-literal language like idioms and metaphors (W3C WCAG 3.0, 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 still draws a pass/fail line for conformance, but its reporting tiers, which measure progress toward and beyond that line, are oddly close to how automated tools already behave. A scanner that returns a 0-100 score, the way a11yFlow does, is already reporting progress rather than a single binary verdict. The move from "pass or fail" to "how far along are you" 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 October 2026 it's still a Working Draft (the tenth, dated 10 September 2026), and W3C says it's "not expected to be a completed W3C standard for a few more years" (W3C, 2026). The working group's schedule aims for a Candidate Recommendation Snapshot in Q4 2027 (AGWG, 2026). 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" (W3C, 2026), and W3C adds that WCAG 2 "will not be deprecated for several years after WCAG 3 is finalized" (W3C WAI, 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?

Not as conformance levels. The March 2026 draft used Bronze, Silver and Gold as its three conformance levels. The 10 September 2026 Working Draft replaced them with a single conformance level (meet every core requirement) and kept the names only for proposed reporting tiers 4 to 6 above it (W3C, 2026). An alternative still under discussion would use a score to show progress and award Bronze, Silver and Gold after conformance.

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 10 September 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, swaps A/AA/AAA for a single conformance level with reporting tiers around it, 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. Bronze, Silver and Gold are no longer how you conform in the current draft, the "174 requirements" figure dates from 2024, 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)