WCAG 3.0: What It Means for Your Plans

WCAG 3.0 is a draft, and the most useful thing you can do about it this year is conform to WCAG 2.2. That isn't a dodge. It's what W3C itself recommends, and it's what the regulations you are actually subject to point toward.

The latest WCAG 3.0 Working Draft is dated September 10, 2026, and W3C says WCAG 3 is not expected to be a completed standard for a few more years. Each new draft brings a wave of webinars and anxious emails, and occasionally someone selling "WCAG 3 readiness." If they call, ask which draft they mean. Here's what the draft is, what it isn't, and what to do in the meantime.

What a Working Draft is, and isn't

W3C standards move through stages. A Working Draft is published so people can read and comment on work in progress. If the work matures, it becomes a Candidate Recommendation, which invites implementation and testing, and eventually a W3C Recommendation, which is what people mean when they call something a standard. Drafts can change a lot between versions, and W3C's own introduction describes WCAG 3 as an incomplete draft that will change.

Three consequences follow:

Nothing in a Working Draft is a requirement. Content can't conform to it, and no regulator is asking you to.
The details will move. Terms, structure, and the conformance model have all shifted between drafts. Planning around a specific draft's details is planning around something its authors expect to revise.
WCAG 2 isn't going away. W3C says WCAG 3 will not supersede WCAG 2, and that WCAG 2 will remain in use for years after WCAG 3 is finished.

What regulations reference today

No regulation we know of requires WCAG 3. Here's what the main ones point to:

Rule	Who it covers	Standard it references
ADA Title II web rule (Justice Department)	State and local governments	WCAG 2.1 Level AA
Section 504 web rule (HHS)	Recipients of HHS funding	WCAG 2.1 Level AA
Revised Section 508 standards	Federal agencies' technology	WCAG 2.0 Level AA
European Accessibility Act	Covered products and services sold to EU consumers	Harmonised standards; EN 301 549's web clauses incorporate WCAG 2.1 A and AA
ADA Title III	Businesses open to the public	No web regulation; settlements commonly reference WCAG 2.x AA

WCAG 2.2 became a W3C Recommendation on October 5, 2023. It added 9 success criteria to WCAG 2.1 and removed 4.1.1 Parsing as obsolete. W3C designed it to be backward compatible: content that conforms to WCAG 2.2 also conforms to 2.1 and 2.0. So the practical rule is simple. Build to WCAG 2.2 AA, and report against whichever version your regulation or contract names.

For WCAG 3 to become a legal requirement in the United States, it would first have to be finished, and then an agency would have to adopt it through rulemaking. Neither step is close.

What the drafts propose differently

With the caveat that all of this is proposed in drafts and may change, W3C describes WCAG 3 as having similar core requirements to WCAG 2, organized differently.

Structure. WCAG 2 is built from success criteria, each a testable statement. The drafts organize content as guidelines written as outcome statements, with requirements beneath them. Recent drafts split requirements into core and supplemental, and add assertions and recommended practices. Methods and how-to material for specific technologies sit alongside as supporting documents. Earlier drafts used "outcomes" for the testable units, which is a good example of how much the vocabulary has moved.

Scope. WCAG 2 is about web content, even though it's widely applied to apps and documents. WCAG 3 is meant to cover web content, apps, tools, publishing, and emerging technologies, and drafts aim to address more user needs, including more needs of people with cognitive and learning disabilities.

Conformance. WCAG 2 conformance is pass or fail for each success criterion at Level A, AA, or AAA. The current draft proposes that conformance requires meeting all core requirements, with requirements tagged by the kind of harm a failure causes and tiers for reporting progress. Earlier drafts proposed bronze, silver, and gold levels and scored ratings instead. Expect this part to change again.

Assertions. The drafts propose assertions: documented claims that an organization followed a particular process, such as testing with disabled users. That's a notable shift, because WCAG 2 conformance gives no credit for process.

Some draft ideas have already caused trouble in production. Earlier drafts explored a different way of measuring text contrast, and teams that redesigned to it risked failing SC 1.4.3 Contrast (Minimum), which is part of every WCAG 2 version the rules above reference. A draft is something to read, not something to ship.

What carries over, whatever WCAG 3 becomes

The work that makes a site conform to WCAG 2.2 is the same work any future version will build on.

Fixed barriers stay fixed. A labeled form field, a keyboard-operable menu, and a focus indicator that's actually visible are correct under every version.
Testing practice. Manual testing with screen readers and keyboards, automated checks in your build pipeline, and usability testing with disabled people. If the drafts' assertions survive, documented process will count for something formal.
Design systems. Accessible components, color tokens that meet contrast, focus styles, and target sizes are fixed once and inherited everywhere. When requirements change, you change the component.
Training and ownership. Designers, developers, and content editors who understand why requirements exist adapt to new wording quickly. Teams that learned the rules as a checklist have to relearn them.
Records. A findings register, decisions, and Accessibility Conformance Reports show where you stood and when, under any standard.

How to read a new draft without losing a week

When a new Working Draft appears, one person can assess it in under an hour. Here's the routine we suggest:

Read the Status of This Document section first. It says what kind of document this is, what changed in scope, and what the working group wants feedback on.
Read the list of changes since the previous draft. Most of what matters for planning is there, and it's much shorter than the draft.
Note how mature each section is. Recent drafts have marked sections by maturity. Anything still described as exploratory is a question the group is asking, not an answer you should build to.
Check it against your components. Does anything touch forms, focus, navigation, authentication, media players, or color? If it doesn't touch a component in your design system, it doesn't touch your roadmap yet.
Write a half-page memo. What changed, what it could mean for your product, and whether to do anything now. The answer to the last question will almost always be no, and writing it down is still worth it.

This keeps the drafts on your radar without letting them drive your plans. It also builds a record. When WCAG 3 does become a Recommendation, you'll have a history of what changed and why, instead of starting cold with a deadline already on the calendar.

What to do now

Conform to WCAG 2.2 AA. Test against it, fix against it, and report against the version your regulation or contract names.
Build the processes that last. Accessibility checks in CI, a design-system audit, role-based training, and procurement language that requires vendors to show test evidence.
Watch the drafts, lightly. Give one person the routine above for each new Working Draft. If something in a draft would hurt your users or can't be tested in practice, say so: W3C takes comments through GitHub issues and its public comments list.
Don't wait. Waiting for WCAG 3 means years of barriers for real users and no change in your current obligations. W3C itself says meeting WCAG 2.2 is the best preparation for WCAG 3.

Next steps that hold up under any version

If you want to know where you stand against WCAG 2.2 AA today, our accessibility audit tests every A and AA criterion with real assistive technology and ranks findings by who is blocked. To make the gains stick through whatever comes next, Accessible Development & Training builds the CI checks, design-system reviews, and team habits that carry over from one version of the guidelines to the next.

Planning for WCAG 3 without the panic