Category: Standards and Guidelines

WCAG 3.0

Also known as: WCAG 3.0, W3C Accessibility Guidelines 3.0, WCAG 3

Simply put

WCAG 3.0 is a set of accessibility guidelines being developed by the W3C to help make digital content easier to use for people with disabilities. It is intended to cover not only web pages but also apps, tools, and publishing content. As of the evidence available, WCAG 3.0 is still in development as a working draft and is not yet a finalized standard, so current accessibility work generally continues to rely on established WCAG 2.x guidelines.

Formal definition

The W3C Accessibility Guidelines (WCAG) 3.0 is a draft standard under development by the W3C through the Web Accessibility Initiative (WAI). It is intended to broaden the scope of prior WCAG versions by applying to web content, applications, tools, and publishing, and by addressing a wider range of disabilities. WCAG 3.0 is also expected to introduce a new conformance model designed to suit people and organizations producing digital assets and technology of varying types, differing structurally from the pass/fail success-criteria model used in WCAG 2.0, 2.1, and 2.2. Because WCAG 3.0 remains a working draft rather than a completed W3C Recommendation, its content and conformance approach may change before finalization, and it should not currently be treated as an adoptable conformance target; WCAG 2.x versions (with Level AA most commonly cited) remain the prevailing reference for conformance work. This entry is informational and not legal advice; readers should consult current W3C publications, applicable regulations, and qualified legal counsel regarding requirements in their jurisdiction.

Why it matters

WCAG 3.0 matters because it represents the W3C's effort to broaden the reach of accessibility guidance beyond traditional web pages to include applications, tools, and publishing content, while addressing a wider range of disabilities. For organizations that plan long-term accessibility strategies, understanding the direction of WCAG 3.0 can inform future roadmaps, even though it is not yet an adoptable standard.

Equally important is understanding what WCAG 3.0 is not. As of the available evidence, WCAG 3.0 remains a working draft rather than a finalized W3C Recommendation, meaning its content and proposed conformance model may change before completion. Treating a draft as a fixed compliance target could lead organizations to invest against requirements that shift, or to overlook the guidelines that are actually referenced in current accessibility work. For that reason, WCAG 2.x versions, with Level AA most commonly cited, remain the prevailing reference for conformance efforts today.

Because the ADA and other US authorities do not codify a specific WCAG version as a universal legal mandate, and because requirements evolve through regulation and case law, organizations should be cautious about drawing legal conclusions from a draft standard. This entry is informational and not legal advice; readers should consult current W3C publications, applicable regulations, and qualified legal counsel regarding requirements in their jurisdiction.

Who it's relevant to

Accessibility engineers and developers

Technical practitioners may monitor WCAG 3.0's development to anticipate how a new conformance model and expanded scope could affect future testing and implementation. In the meantime, they should continue to base conformance work on WCAG 2.x, keeping in mind that automated testing detects only a portion of issues and that manual and assistive technology testing are required.

Compliance officers and program managers

Those responsible for accessibility programs can use awareness of WCAG 3.0 to inform long-term planning, while recognizing that it is a draft and not a current compliance benchmark. Present-day programs generally reference WCAG 2.x, with Level AA most commonly cited as a target.

Legal counsel and business leaders

Because WCAG 3.0 remains a working draft and US authorities do not universally codify a specific WCAG version, legal and business stakeholders should avoid treating it as an established requirement. Requirements evolve through regulation and case law, and decisions should be made with qualified legal counsel and reference to current agency guidance.

UX designers and content creators

Designers and creators working across web content, apps, tools, and publishing may find WCAG 3.0's broader scope relevant to future workflows. Until it is finalized, they should design and produce content against established WCAG 2.x guidance.

Inside WCAG 3.0

Working Draft status

WCAG 3.0 (published under the title 'W3C Accessibility Guidelines 3.0') is currently a Working Draft produced by the W3C through the Web Accessibility Initiative. As draft material, its structure, requirements, and terminology may change substantially before any potential future recommendation, and it should not be treated as a settled or enforceable standard.

New conceptual model versus WCAG 2.x

WCAG 3.0 is being developed as a distinct model rather than an incremental update to the WCAG 2.x series. It explores different ways of expressing and structuring accessibility requirements compared to the success-criteria approach used in WCAG 2.0, 2.1, and 2.2.

Proposed alternative to A/AA/AAA levels

The draft explores conformance approaches that differ from the A, AA, and AAA level structure established in WCAG 2.x. Because these approaches are still under development, specific scoring or rating methods described in drafts are subject to revision.

Broader scope of guidance

WCAG 3.0 aims to address accessibility guidance more broadly than WCAG 2.x, but the precise scope, coverage, and testing methods remain in draft and are not yet finalized.

Relationship to WCAG 2.x

WCAG 2.x (2.0, 2.1, and 2.2) remains the stable, currently referenced set of guidelines. WCAG 3.0 does not replace WCAG 2.x at this time, and existing conformance targets continue to rely on the WCAG 2.x series.

Common questions

Answers to the questions practitioners most commonly ask about WCAG 3.0.

Has WCAG 3.0 replaced WCAG 2.x as the standard I should be following?

No. WCAG 3.0 remains a draft published by the W3C through the Web Accessibility Initiative and has not been finalized or issued as a formal recommendation. WCAG 2.x, most commonly cited at the AA level, remains the established and stable standard referenced by organizations, and it continues to be the benchmark most often referenced in settlements and agency guidance. Adopting WCAG 3.0 as your operative standard now would be premature, and its content may change substantially before completion. This is general information and not legal advice; consult qualified legal counsel regarding current obligations.

Does WCAG 3.0 use the same A, AA, and AAA conformance levels as WCAG 2.x?

Not as a direct carryover. WCAG 3.0 has been explored using a different conformance model than the A, AA, and AAA levels familiar from WCAG 2.x, and its structure and terminology have been under development and subject to change. Because the draft is not final, its conformance approach should not be treated as settled. For current conformance targets, rely on WCAG 2.x levels, where AA is the level most commonly cited as a target.

Should my organization start conforming to WCAG 3.0 now to stay ahead?

Generally, no. Because WCAG 3.0 is a working draft that may change before it is finalized, building a compliance program around it now carries the risk of investing in requirements that shift. The more defensible approach is to work toward WCAG 2.x conformance, commonly at the AA level, while monitoring WCAG 3.0's development. Requirements evolve through regulation, agency rulemaking, and case law, so watching those developments alongside the draft is prudent.

How should I track the progress of WCAG 3.0?

The authoritative source is the W3C and its Web Accessibility Initiative, which publish drafts and status updates for the guidelines they develop. Following official W3C publications rather than vendor summaries or marketing materials is the most reliable way to understand the draft's current state, since third-party characterizations may not reflect the standard as published.

Will meeting WCAG 3.0, once finalized, guarantee legal compliance or an accessible experience?

Meeting any version of WCAG does not by itself guarantee legal compliance or an experience that is accessible to all users. Automated testing detects only a portion of issues, and manual testing along with assistive technology testing is generally required to evaluate real-world usability. Conformance, usability, and legal compliance are distinct considerations, and this remains true regardless of which version of the guidelines is used.

If WCAG 3.0 is finalized, will my existing WCAG 2.x work carry over?

Because WCAG 3.0 is still in development, the relationship between it and WCAG 2.x conformance is not settled, and no definitive migration path should be assumed. In the meantime, work invested in meeting WCAG 2.x, commonly at the AA level, addresses the standard most widely referenced today. Consult current W3C guidance for transition information as the draft matures, and treat any transition planning as provisional until the standard is finalized.

Common misconceptions

WCAG 3.0 is finalized and organizations should conform to it now.

WCAG 3.0 is a Working Draft and is not a completed or stable standard. Organizations generally continue to reference the current WCAG 2.x guidelines, and drafts of WCAG 3.0 may change significantly before any potential future publication as a recommendation.

WCAG 3.0 uses the same A, AA, and AAA levels as earlier versions.

WCAG 3.0 is exploring conformance and rating approaches that differ from the A/AA/AAA structure of WCAG 2.x. Because this work is in draft, the eventual model is not settled and should not be assumed to match the earlier level system.

The ADA or other laws now require WCAG 3.0.

WCAG is a set of technical guidelines published by the W3C, not a law. As a Working Draft, WCAG 3.0 is not established as a legal benchmark, and references to WCAG in settlements, regulations, or agency guidance have generally cited WCAG 2.x. Consult qualified legal counsel and current agency rulemaking for applicable requirements.

Best practices

Continue to target the current WCAG 2.x guidelines (commonly Level AA) for conformance, since WCAG 3.0 remains a Working Draft and is not a stable standard.

Treat any WCAG 3.0 draft content as informational only, and expect its structure, terminology, and requirements to change before any potential future recommendation.

Monitor W3C and Web Accessibility Initiative publications to track the development status of WCAG 3.0 rather than relying on secondhand summaries.

Do not assume WCAG 3.0 conformance approaches map onto the A/AA/AAA levels used in WCAG 2.x, as the draft explores different models.

Combine automated testing with manual and assistive technology testing regardless of which guideline version you follow, since conformance alone does not guarantee an accessible experience or legal immunity.

Consult qualified legal counsel and review current agency rulemaking before treating any WCAG version, including drafts, as a legal requirement in your jurisdiction.