Somewhere in your organization, someone has probably said a version of this sentence: "Why put money into accessibility now if WCAG 3.0 is going to change everything anyway?" It sounds reasonable. It is also, functionally, an argument for missing a legal deadline in favor of a document that will not exist in its final form for years.
The Document That Keeps Not Arriving
WCAG 3.0 is real. The World Wide Web Consortium has been developing it in public for years, and the draft was most recently updated on March 3, 2026. But "updated" is not "finished." WCAG 3.0 remains a W3C Working Draft — an official designation meaning the standard is still being debated, restructured, and tested, not a specification any regulator can point to and say "comply with this." The W3C itself does not expect WCAG 3.0 to reach official Recommendation status — the point at which it becomes a stable, citable standard — until roughly 2029.
That is not a rounding error. That is a multi-year gap between where the standard stands today and where regulators, courts, and procurement officers are actually looking.
The Stat: WCAG 3.0 is still a W3C Working Draft last updated March 3, 2026, and it isn't expected to reach official Recommendation status until roughly 2029. (Source: W3C)
Read that timeline the way a compliance officer should: the deadline you have to answer for sits two full years before the standard some people are waiting on even exists in final form.
What's Actually Enforceable Right Now
None of the deadlines with real legal teeth behind them in the United States reference WCAG 3.0. Not one. The Department of Justice's ADA Title II rule for state and local government websites and apps is written against WCAG 2.1 Level AA. The Department of Health and Human Services' Section 504 rule, covering healthcare entities that receive federal funding, is also anchored to WCAG 2.1 AA. Section 508, governing federal agencies and their contractors, likewise points to WCAG 2.0/2.1 AA as the technical benchmark. If your legal team, your auditors, or a plaintiff's attorney evaluates your digital properties this year, WCAG 2.1 AA is the yardstick they'll use — not a document the W3C itself still calls a draft.
Here's how the two standards actually compare in terms of what matters to a compliance decision-maker today:
| WCAG 2.1 AA (Current Legal Anchor) | WCAG 3.0 (Draft) | |
|---|---|---|
| Status | Finalized W3C Recommendation | Working Draft, updated March 3, 2026 |
| Expected final status | Already final | ~2029 (W3C's own estimate) |
| Referenced by DOJ ADA Title II rule | Yes | No |
| Referenced by HHS Section 504 rule | Yes | No |
| Referenced by Section 508 | Yes | No |
| Can be cited in a legal complaint today | Yes | Not meaningfully — it isn't final |
| Scope | Web content | Being expanded beyond web content (see below) |
That table is the entire argument in one place. If a standard isn't in any of the rules that create legal exposure, it cannot be the thing you're optimizing for this budget cycle.
Why the Draft Keeps Moving
WCAG 3.0 isn't stalled because the W3C is disorganized. It's slow because the scope is genuinely larger and more ambitious than WCAG 2.x ever attempted. One sign of that ambition: under the WCAG 3.0 draft, the acronym itself is being redefined. What was "Web Content Accessibility Guidelines" is becoming "W3C Accessibility Guidelines" — a change that reflects an intent to cover more than web content alone, extending toward broader digital products and interactions. That's a meaningful structural shift, and structural shifts in international standards take years to stabilize, get implementer feedback, and pass through the W3C's formal review stages before they reach Recommendation status.
None of that is a criticism of the process. Getting it right matters more than getting it fast, especially for a standard meant to hold up for another decade. But it does mean anyone banking on "WCAG 3.0 will be simpler" or "WCAG 3.0 will replace what I need to do now" is planning around a document whose final shape isn't settled — while a very settled, very citable standard sits in every current regulation.
The Real Cost of "We'll Wait for WCAG 3"
Consider what "waiting" actually means in practice. It means a state agency delays remediation work ahead of its DOJ Title II deadline because someone read a headline about a "new" WCAG version. It means a hospital system treats Section 504 compliance as a moving target instead of a fixed one, when HHS has already fixed it — to WCAG 2.1 AA. It means a large enterprise's legal exposure keeps accumulating in the gap between "we're aware of accessibility" and "we've actually conformed to the standard that's enforced."
That exposure isn't abstract. The WebAIM Million analysis has repeatedly found that roughly 95.9% of home pages tested have at least one detectable WCAG 2 failure — meaning the vast majority of organizations are already behind on the current standard, before any conversation about a future one even starts. Add in baseline population facts that don't change with any standard revision — the CDC estimates roughly 1 in 4 U.S. adults live with a disability, and the WHO estimates about 8.3% of men and 0.5% of women have some form of color vision deficiency — and the population affected by non-conformance today is not a rounding error either.
A Short Timeline Checklist
| Milestone | Status | What It Means For You |
|---|---|---|
| WCAG 2.1 AA | Final, in force | The standard your deadlines are measured against now |
| DOJ Title II / HHS 504 / Section 508 | Legally enforceable now | Reference WCAG 2.1 (or 2.0) AA — not WCAG 3.0 |
| WCAG 3.0 draft update | March 3, 2026 | Still a Working Draft — not citable as a compliance standard |
| WCAG 3.0 Recommendation | Expected ~2029 | Years after your current deadline; plan for 2.1 AA now |
What to Do Instead of Waiting
The practical path is straightforward, even if it isn't glamorous. Treat WCAG 2.1 AA as the fixed target it legally is, because none of the enforceable rules are going to move to accommodate a draft. Build your remediation roadmap, your procurement language, and your vendor contracts around the standard that's already final — not the one still being negotiated in W3C working groups. When WCAG 3.0 does eventually reach Recommendation status, organizations with a mature WCAG 2.1 AA program will be far better positioned to adapt than organizations that spent the interim years waiting for clarity that wasn't coming.
If you don't currently know how your site or application stacks up against WCAG 2.1 AA, that's the gap to close first — not speculation about a 2029 standard. Get a full accessibility audit from WCAG.World and find out exactly where you stand against the rules that are actually enforceable today, before a regulator, a plaintiff's attorney, or a procurement reviewer finds the gap for you.