# WCAG 3.0: Status, Structure and What to Do Now

Source: https://allyway.ai/glossary/wcag-3

WCAG 3.0 (W3C Accessibility Guidelines 3.0) is a W3C Working Draft for the next generation of accessibility guidelines. It covers web content, apps, tools, publishing and emerging technologies, uses a new structure and conformance model, and is not yet a completed standard.

WCAG 3.0 – officially "W3C Accessibility Guidelines (WCAG) 3.0", developed for years under the project name Silver – is the planned successor to the Web Content Accessibility Guidelines 2. It is still a draft: the latest W3C Working Draft is dated 10 September 2026, and W3C says it has several years of work ahead. For websites today, [WCAG](https://allyway.ai/glossary/wcag) 2.2 remains the standard to meet, and that is also W3C's own advice for preparing for WCAG 3.

## What it means

The [WCAG 3 Introduction](https://www.w3.org/WAI/standards-guidelines/wcag/wcag3-intro/) by W3C WAI is clear about the status: "WCAG 3 is not expected to be a completed W3C standard for a few more years." The draft itself states that the final set of requirements will be different from what it contains now, and that it is inappropriate to cite it as anything other than a work in progress.

| | WCAG 2.2 | WCAG 3.0 (draft) |
|---|---|---|
| Status | W3C Recommendation since 5 October 2023, ISO/IEC 40500:2025 | Working Draft, latest 10 September 2026 |
| Scope | Web content | Web content, apps, tools, publishing and emerging technologies |
| Structure | 4 principles, guidelines, testable success criteria | Guidelines with requirements, assertions and supporting methods |
| Conformance | Levels A, AA, AAA | All core requirements must be met; reporting tiers on top |
| Legal use | Referenced by laws and EN 301 549 | Not referenced by laws |

The draft groups its guidelines into topics such as images and media, text and wording, interactive components, input and operation, error handling, animation and movement, layout, consistency across views, process and task completion, policy and protection, help and feedback, and user control. Many familiar ideas from the [POUR principles](https://allyway.ai/glossary/pour-principles) stay, but the numbering and the A/AA/AAA [conformance levels](https://allyway.ai/glossary/wcag-conformance-levels) do not carry over in the same form: W3C writes that to conform to WCAG 3, content must meet all core requirements, with reporting tiers based on requirement tags, supplemental requirements and assertions.

> **Warning:** > **WCAG 2 is not going away soon**
> According to W3C, WCAG 3 will not supersede WCAG 2, and WCAG 2 will not be deprecated for several years after WCAG 3 is finalized. Laws such as the [European Accessibility Act](https://allyway.ai/glossary/european-accessibility-act) work through standards based on WCAG 2.

## Examples

Your accessibility statement and contracts should name the version you actually test against – today that is WCAG 2.2:

```html title="Example"
<h2>Standard</h2>
<p>We aim to meet WCAG 2.2 Level AA. We follow the development
of WCAG 3.0, which is still a W3C draft.</p>
```

**Do:** Do

Meet WCAG 2.2 AA now, follow the W3C drafts and comment on them if your field is affected, and design for real users – that work carries over.

**Don't:** Don't

Claim "WCAG 3 conformance", wait for WCAG 3 before fixing barriers, or rely on numbers and scores from a draft that W3C says will change.

## How to prepare for WCAG 3.0



## Questions

Q: Is WCAG 3.0 released?
A: No. WCAG 3.0 is a W3C Working Draft; the latest version is dated 10 September 2026. W3C does not expect it to be a completed standard for a few more years.

Q: When will WCAG 3.0 be finished?
A: W3C has not published a completion date. It only says WCAG 3 is not expected to be a completed standard for a few more years.

Q: Will WCAG 3.0 replace WCAG 2.2?
A: Not soon. 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.

Q: Does WCAG 3.0 still use levels A, AA and AAA?
A: The draft uses a different model: content must meet all core requirements, and reporting tiers build on that. Details may still change.

Q: What should I do about WCAG 3.0 today?
A: Meet WCAG 2.2 success criteria – that is W3C's own recommendation. The [free WCAG scanner](https://allyway.ai/free-wcag-accessibility-scanner-for-websites) shows where a page stands against WCAG 2.2 AA in seconds.
