Compliance & Lawsuits

WCAG 3 Readiness: What to Watch, What Not to Refactor For

Last updated May 25, 2026

Buyer questions about WCAG 3 are rising — the next version of the web's accessibility standard has been visible in W3C drafts for years, and product owners want to know if they should be writing tickets against it. The honest answer is no, not yet. The current W3C WCAG 3 Working Draft states verbatim in its “Status of This Document” section: “This is a draft document and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to cite this document as other than a work in progress.” The W3C WAI's WCAG 3 Introduction is just as direct: “Many aspects of W3C Accessibility Guidelines (WCAG) 3 are in an exploratory or developing phase and will change substantially.”

So this page is a readiness brief, not a refactor brief. We'll explain what WCAG 3 is, describe the proposed conformance scoring honestly (including the fact that the historical “bronze/silver/gold” naming is itself part of what has been in flux), separate the parts that are likely directionally durable from the parts that are volatile, and tell you exactly what to ship against today. If you remember nothing else: keep targeting WCAG 2.2 AA, and use the WCAG 3 work to inform longer-horizon design choices — not your next sprint.

What WCAG 3 is

WCAG 3 is the in-progress successor effort to WCAG 2.x, developed by the W3C Accessibility Guidelines Working Group (AG WG) under the Web Accessibility Initiative. The intent, as described in the WAI introduction, is to broaden the scope beyond what WCAG 2.x covers — more disabilities (including a more serious treatment of cognitive and learning disabilities, and people who use augmentative and alternative communication), more content types (apps, XR, immersive media, voice interfaces), and a testing model that allows for measured outcomes rather than binary pass/fail Success Criteria.

The WAI is explicit about timeline: per the WCAG 3 Introduction, “WCAG 3 is not expected to be a completed W3C standard for a few more years.” That is W3C Process language for “multiple Working Draft cycles, then a Candidate Recommendation, then implementation evidence, then a Proposed Recommendation, then Recommendation.” When WCAG 2.1 went through this it took several years; WCAG 3 is a much larger surface area.

Bronze, silver, gold — the proposed scoring model

Earlier WCAG 3 drafts proposed a three-tier conformance model with the labels bronze, silver, and gold, intended to replace the WCAG 2.x Level A / AA / AAA structure. The proposed shape, at the point those names were in active use, looked roughly like this:

• Bronze— the minimum conformance level. Roughly analogous in spirit to today's Level AA: the floor needed for an accessibility claim.
• Silver — an intermediate level requiring additional outcomes and broader coverage than bronze.
• Gold — the highest level, adding outcomes that go beyond the silver threshold.

That said: the current WCAG 3 Working Draft does not lock in the bronze/silver/gold labels — and the WAI has flagged the conformance model itself as one of the major open questions. The WCAG 3 Introduction notes that “developing and vetting the conformance model is a large portion of the work AG needs to complete.” So whatever tiered structure ships in the eventual Recommendation may keep the metal-medal naming, replace it, or pair it with something different entirely. Plan around the structural idea — tiered, outcome-driven conformance — not the specific labels.

What's likely durable vs what's likely to change

A useful way to read WCAG 3 today is to separate the directional shifts (the parts likely to survive in some form) from the specific mechanics (likely to be rewritten more than once before publication).

Likely directionally durable:

• Broader disability coverage. More explicit attention to cognitive and learning disabilities, to users of AAC, and to people with multiple disabilities. The intent here has been consistent across WCAG 3 drafts.
• Outcomes-based testing. Moving away from a single binary “pass / fail” per Success Criterion toward measured outcomes (e.g. “how often” not just “ever”) and a richer mix of machine, human, and process-based tests.
• Broader content coverage. Apps, XR, voice interfaces, and emerging interaction surfaces being addressed directly rather than shoehorned into web-only criteria.
• Tiered conformance (in some form). A graduated model with a defined floor and additional levels above it is consistent across drafts, even if the labels and thresholds change.

Likely volatile (do not refactor against these):

• The specific score thresholds, weights, and metric definitions.
• The exact list of guidelines, outcomes, and methods — the WAI states plainly that “guidelines and requirements will be edited, added, combined, and removed.”
• The conformance-level labels (bronze / silver / gold may stay, change, or disappear).
• How “views” and assistive-technology testing are formally scored.

What to ship against today

Until WCAG 3 reaches Recommendation, the standard to ship against is WCAG 2.2 Level AA. That is the version every current accessibility law and procurement standard cites — ADA Title II (effective for state and local governments through 2026 and 2027 phased deadlines), the European Accessibility Act via EN 301 549, Section 508 in U.S. federal procurement, AODA in Ontario, and the national EAA transpositions across the EU. WCAG 2.2 is a superset of WCAG 2.1, so 2.1 AA remains a valid target where law has not yet been updated.

For the full WCAG 2.x picture see our main WCAG guide and the practical WCAG 2.2 checklist. If you need to explain the A / AA / AAA structure to a stakeholder, our conformance levels page breaks down what each level requires and why AA is the universal legal target. For the testing methodology that gets you there, the accessibility testing guide covers the automated + manual mix.

Where to follow the work

If you want to track WCAG 3 without committing engineering time, three sources are enough:

• The current W3C WCAG 3 Working Draft on the W3C TR namespace — the canonical specification text, updated as drafts are published.
• The W3C Accessibility Guidelines Working Group home page — meeting notes, charter, current participants, open issues.
• The public-agwg-comments mailing list — where the public review feedback is collected, archived, and addressed by the working group.

Subscribing to public-agwg-comments is the lowest-effort way to see which sections are actually moving — if a section gets weeks of back-and-forth, that's where the next draft will likely differ.

How SweepHound helps

SweepHound targets WCAG 2.1 / 2.2 AA today, using the axe-core and IBM Equal Access engines on every paid plan. That is the standard your regulators, customers, and procurement teams care about right now — the same standard EN 301 549 and the ADA reference. When WCAG 3 becomes a W3C Recommendation and the engines we depend on publish stable WCAG 3 rules, we'll update the scan to cover it. Until then, no scanner — ours or anyone else's — can honestly “test WCAG 3.”

The pragmatic path: ship readiness against WCAG 2.2 AA today, treat WCAG 3 as background reading for design and product decisions with multi-year horizons, and revisit the conformance model when the W3C moves the draft to Candidate Recommendation. To see what a dual-engine WCAG 2.2 scan flags on your site, start a free scan. Paid tiers — see pricing — add scheduled re-scans, authenticated scanning, and the accessibility statement generator.