W3C Working Draft — not yet ratified

WCAG 3.0 (Draft)

The W3C Web Content Accessibility Guidelines 3.0 Working Draft (March 2026) introduces a fundamentally new outcomes-based architecture with 174 outcomes and three conformance levels: Bronze, Silver, and Gold. No law or regulation references WCAG 3.0. A W3C Recommendation is not expected before 2028–2029.

DraftW3C / WAIDraft (March 2026)

What is WCAG 3.0 (Draft)?

WCAG 3.0 (Web Content Accessibility Guidelines 3.0), under development by the W3C Web Accessibility Initiative (WAI) since 2019, represents a fundamental rethinking of the guidelines structure compared to WCAG 2.x. Rather than success criteria with pass/fail binary evaluation, WCAG 3.0 uses outcomes — broader accessibility goals evaluated on a scoring scale. The March 2026 Working Draft contains 174 outcomes organized around the same POUR principles (Perceivable, Operable, Understandable, Robust) with additional focus on cognitive accessibility and emerging interaction paradigms. Three conformance levels replace the familiar A/AA/AAA: Bronze (minimum), Silver (intermediate), and Gold (comprehensive).

WCAG 3.0 is not referenced by any law or regulation as of May 2026. It is relevant to: (1) organizations planning long-term accessibility roadmaps who want to understand where the W3C is heading; (2) accessibility specialists and auditors who need to understand the structural differences from WCAG 2.x; (3) developers building new platforms from scratch who want to design for future compliance. Organizations currently required to comply with WCAG 2.1 or 2.2 AA (under EAA, Section 508, RGAA, ADA) should continue targeting WCAG 2.2 AA — WCAG 3 will not replace these obligations for many years after ratification.

As of March 2026, WCAG 3.0 is a Working Draft, the earliest stage of the W3C process. It must progress through Working Draft → Candidate Recommendation → Proposed Recommendation → Recommendation. W3C estimates a Candidate Recommendation no earlier than Q4 2027 and a full Recommendation in 2028–2029. Even after reaching Recommendation status, WCAG 3 will require years of transposition into national law and harmonized standards (EN 301 549, RGAA, etc.) before triggering legal obligations. Organizations should not delay current WCAG 2.2 AA compliance efforts waiting for WCAG 3.0.

Key criteria

The 10 requirements most frequently flagged in automated audits by scan-access.com.

Outcome: Alt text
Text alternatives for non-text content (retained outcome)
WCAG 3.0 retains the core concept of text alternatives for images, but evaluates it as an outcome rather than a binary pass/fail. Scoring considers context, quality of alt text, and coverage across the page.
Official spec →WCAG 1.1.1
Outcome: Contrast
Visual contrast (new scoring model)
WCAG 3.0 introduces a new contrast algorithm (APCA — Advanced Perceptual Contrast Algorithm) that is more perceptually accurate than the WCAG 2.x ratio formula. Bronze level maps approximately to WCAG 2.x AA.
Official spec →WCAG 1.4.3
Outcome: Keyboard
Keyboard operability (retained outcome)
WCAG 3.0 retains keyboard accessibility as a core outcome. The evaluation model scores keyboard support more holistically than WCAG 2.1's binary criterion 2.1.1.
Official spec →WCAG 2.1.1
Bronze
Bronze conformance level
Bronze is the minimum WCAG 3.0 conformance level, intended to align roughly with WCAG 2.x Level AA. Organizations targeting WCAG 2.2 AA today are effectively preparing for Bronze.
Official spec →
Silver
Silver conformance level
Silver targets a higher accessibility bar than Bronze, incorporating more cognitive accessibility outcomes and testing with real users with disabilities as part of the evaluation process.
Official spec →
Gold
Gold conformance level
Gold is the highest conformance level, requiring comprehensive coverage across all 174 outcomes including advanced cognitive and situational disability considerations.
Official spec →
Outcome: Cognitive
Cognitive accessibility outcomes (new emphasis)
WCAG 3.0 significantly expands cognitive accessibility coverage compared to WCAG 2.x, with dedicated outcomes for clear language, consistent interfaces, reduced distractions, and error prevention.
Official spec →
Outcome: Timing
Adequate time (retained, broadened)
WCAG 3.0 broadens time limit requirements to address a wider range of timed interactions, including moving content and auto-updating information, with scoring rather than pass/fail.
Official spec →WCAG 2.2.1
New structure
Outcomes-based architecture (fundamental change)
The shift from pass/fail success criteria to scored outcomes means conformance claims in WCAG 3.0 will be richer and more nuanced than WCAG 2.x. Automated tools cover a smaller proportion of outcomes.
Official spec →
174 outcomes
174 outcomes (March 2026 draft count)
The March 2026 Working Draft contains 174 outcomes. This number is subject to change — some outcomes may be merged, split, or removed before Candidate Recommendation. The structure is not yet stable.
Official spec →

scan-access.com coverage

Prepare for WCAG 3.0 by mastering WCAG 2.2 AA today

WCAG 3.0 does not yet require compliance from any organization. The most effective preparation for WCAG 3.0's eventual adoption is to achieve WCAG 2.2 AA compliance now — Bronze level in WCAG 3.0 maps approximately to WCAG 2.x AA. scan-access.com's axe-core 4.11 engine covers ~35% of WCAG 2.2 AA criteria automatically, providing the foundation for a WCAG 2.2 → Bronze transition strategy. As WCAG 3.0 progresses toward Candidate Recommendation, scan-access.com will add WCAG 3.0 outcome tracking. Subscribe to be notified when WCAG 3.0 support is available.

Start with WCAG 2.2 AA today

Free scan against WCAG 3.0 (Draft). No account required.

Frequently asked questions

When will WCAG 3.0 be released?

WCAG 3.0 is currently a Working Draft (March 2026). The W3C process requires: Working Draft → Candidate Recommendation → Proposed Recommendation → Recommendation. W3C WAI estimates a Candidate Recommendation no earlier than Q4 2027 and a final Recommendation in 2028–2029. Even after reaching Recommendation, WCAG 3.0 must be transposed into harmonized standards (EN 301 549) and national law before triggering legal obligations — a process that typically takes 2–5 additional years.

What's new in WCAG 3.0 compared to WCAG 2.2?

WCAG 3.0 introduces fundamental structural changes: (1) outcomes instead of pass/fail success criteria; (2) scored conformance instead of binary compliance; (3) three levels (Bronze/Silver/Gold) instead of A/AA/AAA; (4) a new contrast algorithm (APCA) replacing the WCAG 2.x formula; (5) significantly expanded cognitive accessibility coverage; (6) testing with real users as part of Silver/Gold conformance. The core principles (POUR) are retained.

Is WCAG 3.0 the same as WCAG 2.2?

No — WCAG 3.0 is a new standard, not an update to WCAG 2.x. It uses a different architecture (outcomes vs. success criteria), different conformance model (scored vs. pass/fail), and different levels (Bronze/Silver/Gold vs. A/AA/AAA). Bronze conformance in WCAG 3.0 is intended to approximate WCAG 2.x AA, but the evaluation methodology is fundamentally different. Content that meets WCAG 2.2 AA is not automatically WCAG 3.0 Bronze-conformant; a separate assessment is required.

Should organizations start complying with WCAG 3.0 now?

No legal obligation to comply with WCAG 3.0 exists as of 2026. Organizations with current compliance obligations (EAA, Section 508, RGAA, ADA) should focus on WCAG 2.2 AA. The best preparation for WCAG 3.0 is to achieve WCAG 2.2 AA compliance (which maps approximately to Bronze) and to build accessible-by-default development practices. Monitor W3C WAI announcements for the Candidate Recommendation, which will be the signal to begin detailed WCAG 3.0 gap analysis.

What is the APCA contrast algorithm in WCAG 3.0?

APCA (Advanced Perceptual Contrast Algorithm) is a new contrast measurement method proposed for WCAG 3.0 that better models human visual perception than the WCAG 2.x formula. WCAG 2.x uses a luminance contrast ratio (e.g., 4.5:1); APCA uses a more complex algorithm that accounts for font weight, size, and polarity (light text on dark vs. dark text on light). APCA is not yet final — it is part of the WCAG 3.0 Working Draft and subject to change.