WCAG 3.0 Explained: What Changes & When It's Actually Required (2026)
What WCAG 3.0 Means (and When It Actually Matters)
If you've seen headlines warning that "WCAG 3.0 changes everything," take a breath. WCAG 3.0 is real and it's a big shift — but it's still an early draft, and no law will require it for years. Here's the honest version: what's changing, how it differs from WCAG 2.2, and when (and whether) you actually need to act.
TL;DR
- WCAG 3.0 is not required yet. It's a W3C Working Draft (updated March 2026). A final standard isn't expected before 2028.
- The model changes from pass/fail A/AA/AAA to an outcomes-based score with Bronze, Silver and Gold levels.
- Bronze ≈ today's WCAG 2.2 AA. So meeting 2.2 AA now is the best possible head start.
- What to do today: keep conforming to WCAG 2.2 AA — that's what the ADA, Section 508 and the EAA reference right now.
What is WCAG 3.0?
WCAG 3.0 is the next major version of the Web Content Accessibility Guidelines from the W3C's Accessibility Guidelines Working Group. The W3C published an updated WCAG 3.0 Working Draft in March 2026, and the authoritative background and timeline live in the WCAG 3 Introduction.
It's not a small update like 2.1 → 2.2. WCAG 3.0 rethinks how accessibility is measured. The March 2026 draft reorganizes guidance into a much larger set of outcome-based requirements (reported at around 174) and introduces a flexible scoring system in place of the familiar checklist.
WCAG 3.0 changes: what's actually different
1. Pass/fail is replaced by a scoring model
WCAG 2.2 is binary: each success criterion passes or fails. WCAG 3.0 introduces graded outcomes that better reflect real user experience, rolling up into an overall conformance level.
2. Bronze, Silver, Gold replace A / AA / AAA
Bronze covers the foundational requirements — broadly equivalent to WCAG 2.2 AA. Silver requires a higher score and represents genuinely good accessibility. Gold is aspirational, covering thorough accessibility including complex cognitive and low-vision needs.
3. Broader coverage and scope
WCAG 3.0 expands guidance for cognitive disabilities and low vision, explores newer approaches to contrast (such as APCA), and is designed to apply beyond traditional web pages to apps and other digital products.
The honest take: these are meaningful improvements, but they're still moving. A Working Draft can — and will — change before it becomes a standard. Building your compliance program around a draft today would mean chasing a moving target.
WCAG 3.0 vs 2.2 at a glance
| Aspect | WCAG 2.2 (current) | WCAG 3.0 (draft) |
|---|---|---|
| Status | W3C Recommendation (in force) | Working Draft (not final) |
| Grading | Pass/fail success criteria | Outcomes-based scoring |
| Levels | A, AA, AAA | Bronze, Silver, Gold |
| Scope | Primarily web content | Web, apps and other digital products |
| Referenced by law? | Yes — ADA, Section 508, EAA | Not yet |
When is WCAG 3.0 required?
This is the question that matters most, and the honest answer is: not for a long time. Per the W3C's own timeline, a Candidate Recommendation is anticipated around Q4 2027, and a final W3C Recommendation is not expected before 2028. Even after that, regulators take additional years to reference a new version in law.
Right now, every major accessibility law points to WCAG 2.x: U.S. ADA settlements, Section 508, and the European Accessibility Act all reference WCAG 2.1 / 2.2. So WCAG 2.2 AA is the bar you're actually measured against today — and will be for the foreseeable future.
What you should do now
You don't need to "get ready for WCAG 3.0." You need to be genuinely accessible — and that automatically prepares you for it:
- Meet WCAG 2.2 AA. It's required today and maps to WCAG 3.0 Bronze. Nothing you do here is wasted.
- Find your gaps. Run a free website accessibility scan to see where you stand against WCAG 2.2.
- Fix real issues, not just symptoms. Remediation and an audit trail matter far more than a draft you can't be measured against yet. See how WebAbility remediates.
- Stay informed, not anxious. Follow the W3C WAI news for draft updates — and ignore vendors using WCAG 3.0 to manufacture urgency.
See where your site stands on WCAG 2.2 today
Skip the WCAG 3.0 hype. Run a free scan, fix what actually counts, and you'll already be on the path to Bronze.
Run my free WCAG scan →Frequently asked questions
When is WCAG 3.0 required?Not yet, and not for years. As of 2026 it's a Working Draft; a Candidate Recommendation is anticipated around Q4 2027 and a final Recommendation no earlier than 2028. Today's laws reference WCAG 2.x, so WCAG 2.2 AA is what you're measured against.
What's the difference between WCAG 3.0 and WCAG 2.2?WCAG 2.2 uses pass/fail criteria graded A/AA/AAA. WCAG 3.0 uses outcomes-based scoring with Bronze/Silver/Gold levels, and broadens coverage of cognitive and low-vision needs. Bronze is roughly equivalent to WCAG 2.2 AA.
Should I wait for WCAG 3.0 before fixing my website?No. Waiting leaves you non-compliant with current laws. Meeting WCAG 2.2 AA now is the best preparation for WCAG 3.0.
Will my WCAG 2.2 work be wasted under WCAG 3.0?No. WCAG 3.0 builds on the same principles; your 2.2 AA work forms the foundation of WCAG 3.0 Bronze conformance.
Sources- W3C — WCAG 3.0 Working Draft (updated March 2026)
- W3C WAI — WCAG 3 Introduction (background & timeline)
- W3C WAI — For Review: WCAG 3 Working Draft – March 2026
- W3C — WCAG 2.2 Recommendation
Quick Questions
Tap to ask AI about this article
