Blog ·

WCAG 3 changed its conformance model. Your audit report doesn't have to.

The September 2026 WCAG 3 draft replaces its conformance model with Tiers 1–6. Here's what that means for your next accessibility audit (short answer: keep testing against WCAG 2.2 AA).

On September 10, the W3C published a new Working Draft of WCAG 3. The biggest change is in how conformance works, and the W3C has asked the public for comments on it.

If you run a website for a university department, a clinic or a nonprofit, you may have already gotten a forwarded link with "do we need to worry about this?" attached. Here's the short answer, then the longer one.

Short answer: No. Keep testing against WCAG 2.2 Level AA. The W3C says so itself.

What changed in the September draft

Earlier WCAG 3 drafts kicked around ideas like bronze, silver and gold levels. The new draft takes a different route:

  • There's one conformance level. To conform, a site has to meet all of WCAG 3's core requirements.
  • Every core requirement gets one or more tags: Physical harm, Risk, Barrier and Friction.
  • Progress is reported in tiers, numbered 1 through 6. Tier 3 means you conform. Tiers 1 and 2 show progress toward conformance. Tiers 4 to 6 go beyond it by adding supplemental requirements. The exact numbers are still being decided.
  • Scoring is a side proposal. The draft's Explainer includes an alternative approach that would use the same tags to give you a score instead of a tier. It isn't the main proposal.

The thinking is sound. A site that fixed every seizure risk but still has some clunky forms is in a different place than a site that hasn't started, and a pass/fail label hides that difference. Tiers are meant to show it.

What didn't change

This part is what matters for your budget and your next audit:

  • WCAG 3 is still a draft. The W3C says it "is not expected to be a completed W3C standard for a few more years."
  • WCAG 3 won't replace WCAG 2. WCAG 2 won't be deprecated until several years after WCAG 3 is finished.
  • The W3C's own advice is to meet WCAG 2.2 now as the best way to prepare for WCAG 3.

Laws, contracts and procurement rules point to WCAG 2.x, and so do the demand letters that show up in inboxes. A draft standard changes none of that.

What your audit report can borrow today

You don't have to wait for WCAG 3 to get its main benefit. When we write up an audit, we sort every WCAG 2.2 AA failure by how much it hurts real people:

SeverityWhat it looks likeExample
HarmCould physically hurt someoneContent that flashes more than three times a second
BlockerSomeone can't finish the taskA "Donate" button you can't reach with a keyboard
BarrierSomeone can finish, but only with real effortForm errors that are announced only by color
FrictionAnnoying, slows people downLink text that just says "click here"

Those categories line up closely with WCAG 3's tags. So your report stays tied to the standard you're actually measured against, and it already reads the way WCAG 3 will. Your board gets a clear priority list instead of a 140-row spreadsheet.

Should you comment on the draft?

If your organization has opinions, yes, and higher-ed, healthcare and nonprofit teams have useful ones. The W3C asks three questions:

  1. Does a single conformance level with tagged reporting tiers improve on earlier drafts?
  2. What are the pros and cons of tiers versus the alternative scoring approach?
  3. In your role, how would you use reporting tiers that lead to conformance and go beyond it?

You can open an issue in the WCAG 3 GitHub repository, or email public-agwg-comments@w3.org if GitHub isn't practical. The announcement doesn't give a deadline, so sooner is better.

The bottom line

Read the draft if you're curious, and comment if you have a view. Then go back to fixing the WCAG 2.2 AA issues on your site. That work counts today, and it will still count under WCAG 3.

Want a plain-language accessibility review of your site, sorted by what to fix first? Get in touch.