WCAG 3.0 is the next generation of the Web Content Accessibility Guidelines, and as of the W3C working draft dated September 10, 2026 it is still a draft: not a standard, not referenced by any law, and years from final publication. The W3C’s own introduction, updated September 25, 2026, puts it plainly: WCAG 3 “is currently an incomplete draft that will change” and “is not expected to be a completed W3C standard for a few more years.” It will eventually replace the A, AA and AAA levels of WCAG 2 with core requirements plus graded tiers, cover more disabilities and more technologies, and change how conformance is scored. What it will not do is invalidate the work you are doing today. In the W3C’s words, “the best way to prepare for WCAG 3 in the future is to meet WCAG 2.2 success criteria now.”

This explainer covers what is in the current draft, what is different from WCAG 2, what the timeline looks like, and what a business or web team should actually do about it in 2026. For the standard in force today, see the WCAG glossary entry and our WCAG 2.2 checklist.

Where WCAG 3.0 stands in September 2026

  • Status: W3C Working Draft, last updated September 10, 2026, with a companion explainer published the same day and an updated public introduction on September 25. The W3C marks each section of the draft with a maturity level (Placeholder, Exploratory, Developing, Refining, Mature); the guidelines themselves are marked “Developing,” meaning the direction is roughly agreed but details are still being worked out.
  • Size: the March 2026 draft reorganized the earlier “outcomes” into 174 “requirements,” a deliberate change of language from something to aim for to something you must meet. Expect that count to move.
  • Constraint: the working group’s explainer states that WCAG 3 will not be published until it covers at least as much as WCAG 2.2. It cannot become the standard while offering less protection than the one it replaces.
  • Timeline: the W3C has not committed to a date beyond “a few more years.” Third-party estimates from accessibility consultancies put a Candidate Recommendation around late 2027 and a final Recommendation no earlier than 2028, and those estimates have slipped before. WCAG 2.0 (December 2008) took nine and a half years to reach 2.1 (June 2018); the safe assumption is that 3.0 will not be a legal reference point before 2029 at the earliest.

What changes from WCAG 2

The structure

WCAG 2 has principles, guidelines and numbered success criteria (1.4.3 Contrast, and so on). WCAG 3 keeps the idea of guidelines as plain-language outcome statements but replaces success criteria with three kinds of provision:

  • Requirements, which are testable and tagged as either core (needed for conformance) or supplemental (needed for the higher tiers).
  • Assertions, which are claims an organization makes about its process rather than its output: that it has an accessibility style guide, that it runs usability testing with people with disabilities, that it reviews policy. These are new. WCAG 2 has nothing like them.
  • Methods, which are technology-specific ways to meet a requirement, kept separate so the standard can outlive any particular technology.

The conformance model

This is the biggest change. WCAG 2 conformance is binary per page and per level: a page meets AA or it does not. The WCAG 3 draft replaces the A/AA/AAA ladder with a single conformance line and tiers on either side of it. Every requirement carries a severity tag (Physical harm, Risk, Barrier or Friction), and the tiers are built from those tags. As the W3C’s introduction currently describes them:

  • Tier 1: all Physical harm and Risk requirements are met.
  • Tier 2: Physical harm, Risk and Barrier requirements are met.
  • Tier 3, conformance: all core requirements are met. This is the one line that corresponds to “conforms.”
  • Tiers 4 to 6: progressively add supplemental requirements, assertions, and organization-level assertions.

The explainer refers to the tiers below conformance as “Avoid physical harm” and “Foundational access,” and to the tiers above it as Bronze, Silver and Gold; the numbered names and the metal names describe the same structure and both may change. Two things are new either way. An organization can report progress before it fully conforms, which WCAG 2 never allowed. And failures are weighed rather than just counted: a flashing animation that could trigger a seizure and a slightly vague link label are both failures in WCAG 2, but in WCAG 3 they are not treated as equivalent.

The draft has also explored scoring and decision-tree testing, where a tester works through a series of questions rather than a yes-or-no check. Those parts are among the least settled and may not survive in their current form.

The scope

WCAG 2 is scoped to web content. WCAG 3 is named “W3C Accessibility Guidelines” (the W is no longer “Web”) and is intended to cover web content, apps, tools, publishing, and emerging interfaces. It also aims to address needs that WCAG 2 handles thinly, particularly cognitive and learning disabilities and low vision, which is where many of the 174 requirements come from.

What stays the same

  • WCAG 2 is not going away. The W3C states that “WCAG 3 will not supersede WCAG 2 and WCAG 2 will not be deprecated for several years after WCAG 3 is finalized.” Regulations that cite 2.0 or 2.1 will keep citing them until each regulator chooses to update. Section 508 still references WCAG 2.0, published in 2008; that is how slowly the legal layer moves.
  • The underlying needs are the same. Text alternatives, keyboard operability, contrast, captions, focus, labels, consistent navigation. The WCAG 3 requirements restate these needs in different words and add to them; they do not contradict them.
  • Well-built sites carry over. The draft states that content conforming to WCAG 2.2 Level A and AA “is expected to meet most of the minimum conformance level” of the new standard, with additional work needed for the rest. Sites built on semantic HTML with accessibility in the code will have the least additional work. Sites patched to pass a scanner will have the most.

What WCAG 3.0 means for the law

Nothing, for now. No regulation anywhere references WCAG 3. In the United States, the ADA Title II rule and the HHS Section 504 rule require WCAG 2.1 AA (with deadlines in 2027 and 2028), Section 508 requires 2.0 AA, and Title III lawsuits settle on 2.0 or 2.1 AA. The European Accessibility Act and EN 301 549 reference 2.1. When WCAG 3 is finally published, each of those will need its own rulemaking or standards update to adopt it, and regulators have historically taken years to do that. A business planning around WCAG 3 in 2026 is planning around something that will not be enforceable this decade.

What to do now

  1. Build and audit to WCAG 2.2 AA. It is the current standard, it satisfies every regulation that cites 2.0 or 2.1, and the W3C names it as the way to prepare for WCAG 3. Our WCAG 2.2 checklist lists every criterion; the ADA compliance website checklist is the shorter, prioritized version.
  2. Fix accessibility in the code, not on top of it. WCAG 3’s severity model will make structural failures (keyboard traps, unlabeled controls, unreadable custom components) weigh more, not less. Overlays and widgets that paper over code will be worth even less under WCAG 3 than they are today.
  3. Start the practices WCAG 3 will reward. The assertion tiers give credit for having an accessibility style guide, testing with people who use assistive technology, and reviewing accessibility in your publishing process. Those are good practice under WCAG 2 as well, and they are what separates a site that stays conformant from one that passes an audit and drifts.
  4. Do not rebuild for WCAG 3. There is nothing to rebuild toward yet. Anyone selling “WCAG 3.0 compliance” in 2026 is selling conformance to a moving draft.
  5. Check back once a year. The working group aims to publish two drafts a year. A yearly look at the W3C’s WCAG 3 introduction is enough to know when the picture changes. We will keep this article current.

Frequently asked questions

Is there a WCAG 2.3?

No. The current version is WCAG 2.2 (October 2023). The W3C has published no plan for a further 2.x release and is putting its effort into 3.0. If you see “WCAG 2.3” referenced, it is either a typo for 2.2 or a misreading of 3.0.

When will WCAG 3.0 be released?

The W3C says only that it is “not expected to be a completed W3C standard for a few more years.” The current draft is from September 2026, sections are still marked Developing or Exploratory, and the working group will not publish until 3.0 covers at least as much as 2.2. Outside estimates point to a Candidate Recommendation in late 2027 and a final Recommendation in 2028 or later. Legal adoption would follow that by years.

Will WCAG 3.0 replace WCAG 2.2?

Not for a long time. The W3C states that WCAG 3 will not supersede WCAG 2, and that WCAG 2 will not be deprecated for several years after WCAG 3 is finalized. Regulations will keep citing 2.x until they are individually updated. Expect a long period where both are in use, the way WCAG 2.0 remained the legal reference in Section 508 long after 2.1 and 2.2 existed.

What are Bronze, Silver and Gold in WCAG 3?

They are the explainer’s names for the tiers above baseline conformance, which the W3C introduction numbers as Tiers 4 to 6. Conformance itself (Tier 3) means meeting all core requirements; the higher tiers are earned by also meeting supplemental requirements and making assertions about your accessibility practices. The names and the exact thresholds are still under discussion and may change.

Will a site that meets WCAG 2.2 AA automatically meet WCAG 3.0?

Not automatically, but close. The W3C expects 2.2 AA content to meet most of the WCAG 3 minimum level, with additional work needed for the new requirements, particularly around cognitive accessibility. A site with accessibility built into its code will need the least additional work.

Build for the standard that is in force, and the one that is coming

Every site we build is developed to WCAG 2.2 AA in the code, which is the foundation WCAG 3 will be measured from. Our ADA compliance services audit and remediate existing sites to the same standard.

Book a Discovery Call →

or call 919-200-0201

Sources