WCAG 3.0 Explained: The Timeline, the Tiers, and Why 2.2 AA Still Rules

WCAG 3.0 is an early, incomplete draft of a future accessibility standard — not something you can comply with, and not something any law references. The W3C’s own status page says WCAG 3 “is not expected to be a completed W3C standard for a few more years” and that much of it “will change substantially.” The practical takeaway for a small business: the WCAG 2.1/2.2 AA work you do now is the preparation for WCAG 3.0, because its minimum tier is being built on top of that exact foundation.

That hasn’t stopped some accessibility vendors from using 3.0 as a sales lever — “buy our subscription and you’ll be future-proof.” So let’s walk through what WCAG 3.0 actually is, when it’s really coming, what Bronze/Silver/Gold and APCA mean, and what (if anything) you should do about it.

What is WCAG 3.0?

WCAG 3.0 — formally the W3C Accessibility Guidelines 3.0 — is the W3C’s long-term project to rebuild accessibility guidance from the ground up. The most recent Working Draft was published March 3, 2026, and it is candid about how unfinished it is: every section carries a maturity label (Placeholder, Exploratory, Developing, Refining, or Mature), and the core Guidelines section is still only marked “Developing.”

Three structural changes stand out versus the WCAG 2.x you may know from our WCAG 2.2 vs 2.1 comparison:

• Outcomes instead of success criteria. WCAG 2 has pass/fail success criteria. WCAG 3 organizes around user-centered “outcomes” supported by requirements, assertions, and technology-specific methods.
• Broader scoring. Instead of binary pass/fail for everything, the draft explores graded evaluation, which could better capture “mostly accessible” versus “completely broken.”
• Wider scope. When the W3C published its expanded list of proposed outcomes, Deque counted 174 new outcomes in the May 2024 draft — including ideas WCAG 2 never touched, like explaining non-verbal cues in media and keeping disability information private.

Note the word running through all of this: proposed. The name “W3C Accessibility Guidelines” (not “Web Content”) signals the ambition, but the content is a moving target by the W3C’s own description.

When will WCAG 3.0 be released?

The honest answer is: years from now, and nobody can give you a firm date. The W3C’s WCAG 3 introduction, updated March 3, 2026, states plainly that “WCAG 3 is not expected to be a completed W3C standard for a few more years.”

Outside trackers put numbers on that. AbilityNet’s February 2026 analysis reports the Candidate Recommendation is “anticipated in Q4 of 2027,” with a final W3C Recommendation “not earlier than 2028.” Deque’s take on the 174-outcome draft was blunter still: “even in the most optimistic scenario, WCAG 3.0 likely won’t be finished before 2028” — and W3C timelines have historically slipped, not accelerated.

And here is the sentence every business owner should keep: according to the W3C, “WCAG 3 will not supersede WCAG 2 and WCAG 2 will not be deprecated for at least several years after WCAG 3 is finalized.” Even on the day WCAG 3.0 ships, WCAG 2.2 remains a valid, current standard.

WCAG 3.0 vs 2.2: what actually changes?

For the everyday work — alt text, keyboard access, labeled forms, readable contrast — surprisingly little changes. The barriers are the same barriers; WCAG 3 mostly changes how they’re organized, tested, and scored.

The bigger philosophical shift is from “did this page pass 50 checkboxes?” toward “can people with disabilities actually complete tasks?” That’s a direction we like, because it matches how manual testing already works: a human with a screen reader trying to finish a checkout tells you more than any checklist. But a philosophy isn’t a compliance target until the scoring math is final, and the March 2026 draft marks its conformance approach as still in development.

Bronze, Silver, and Gold: the proposed tiers

Bronze, Silver, and Gold are WCAG 3.0’s proposed replacement for today’s Level A, AA, and AAA. Per the W3C’s WCAG 3.0 Explainer (Group Note draft, March 3, 2026), Bronze is the minimum level: all pages in scope “MUST satisfy all the core requirements and some portion (to be determined) of the supplemental requirements and assertions.” Silver requires a larger portion of the supplemental set; Gold larger still.

Two details in that explainer matter enormously for planning:

1. The W3C describes the core requirements as “somewhat comparable to WCAG 2.2 Level AA.” Bronze — the entry tier — is essentially the 2.2 AA work with extras layered on.
2. The phrase “to be determined” appears in the definition of the minimum conformance level itself. That’s how unfinished this is.

So when someone implies you should reorganize your compliance program around Bronze/Silver/Gold today, remember: the W3C hasn’t finished defining Bronze. What it has said is that Bronze sits on top of 2.2 AA. Fix your site to WCAG 2.1/2.2 AA now and you are, quite literally, doing the WCAG 3.0 prep work.

APCA explained: the new contrast math

APCA — the Accessible Perceptual Contrast Algorithm — is the candidate contrast model developed for WCAG 3, and it’s the most concrete, testable piece of the whole project. Today’s rule, WCAG 1.4.3, uses a single ratio: normal text needs 4.5:1 against its background. APCA replaces that with a perceptual Lc score that accounts for font size and weight.

The APCA documentation explains the reason for the change: WCAG 2.x “far overstates contrast for dark colors to the point that 4.5:1 can be functionally unreadable when a color is near black.” In other words, the old math can pass color pairs that are genuinely hard to read — especially in dark mode — and fail pairs that are fine. Here are the APCA target levels from that documentation:

Two cautions. First, the March 2026 WCAG 3.0 draft does not lock APCA in — no specific algorithm is normative yet. Second, and more important for you: no legal requirement uses APCA today. If your site is tested — by a plaintiff’s expert, a state agency, or our free contrast checker — the measuring stick is WCAG 2’s 4.5:1. Our color contrast guide covers how to pass the rule that actually applies.

Does any law require WCAG 3.0? No.

No law, regulation, or court standard anywhere references WCAG 3.0 — it’s an unfinished draft, and drafts can’t be adopted into law. Here’s what the major rules actually name:

Notice the pattern: the newest binding standard in that table is WCAG 2.1 — the version at the center of the DOJ’s Title II web rule — and federal procurement still runs on WCAG 2.0. Regulators adopt standards years after they ship. WCAG 3.0 appearing in a US regulation is realistically a 2030s event.

The “future-proof for WCAG 3” sales pitch

If a vendor is using WCAG 3.0 to create urgency — “the rules are changing, subscribe now to stay ahead” — you now have everything you need to evaluate that pitch. There is no WCAG 3.0 to be ready for. The W3C says the draft “will change substantially.” The minimum tier is being defined as 2.2-AA-plus. And no enforcement mechanism on earth references it.

This pitch shows up most often from overlay and widget vendors, whose products already have a documented problem with the current standard: sites running them get sued anyway, because a script layered over broken HTML doesn’t fix the barriers a real user hits. A tool that can’t reliably deliver WCAG 2.1 AA today is not a hedge against a standard that doesn’t exist yet. If you’re evaluating those products, our honest comparison of accessiBe, UserWay, and AudioEye alternatives is the place to start.

To be fair to the other side of this: WCAG 3.0 itself is good, serious work by people who care about disabled users, and following its progress is worthwhile. The FUD is in the selling, not the standard.

What a small business should actually do

Here’s the whole preparation plan, in order:

1. Meet WCAG 2.1 AA now. It’s what the DOJ rule names, what courts look at, and what WCAG 3.0’s Bronze tier is being built on. Start with our free accessibility checker to find the obvious failures.
2. Fix real barriers in real code. Contrast, keyboard access, labels, headings, alt text — via manual remediation, not a widget. These fixes carry forward into any future standard because the underlying human needs don’t change.
3. Pick generous contrast while you’re at it. If a color pair passes 4.5:1 comfortably rather than barely, it’s far more likely to also clear APCA later. Our color contrast checker shows you the ratio for any pair.
4. Ignore WCAG 3.0 deadlines until the W3C publishes one. Check back when a Candidate Recommendation actually lands — on current estimates, that’s late 2027 at the earliest.

That’s it. No subscription required to be “ready.”

WCAG 3.0 is worth understanding and not worth fearing. It’s years away, it won’t invalidate WCAG 2.2, and its entry tier is the work you should be doing anyway. The businesses that get burned won’t be the ones who ignored a draft — they’ll be the ones who ignored the standard that applies right now.

Want to know where your site stands against WCAG 2.1 AA — the standard that’s actually enforced? Run a free accessibility scan.