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.

← All standardsGlobal

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).

Status

W3C / WAI

In force

Draft (March 2026)

Scan coverage

Not yet scannable

Detailed coverage

What ScanAccess detects on WCAG 3.0 (Draft)

Outcome: Alt textText alternatives for non-text content (retained outcome)
Outcome: ContrastVisual contrast (new scoring model)
Outcome: KeyboardKeyboard operability (retained outcome)
BronzeBronze conformance level
SilverSilver conformance level
GoldGold conformance level
Outcome: CognitiveCognitive accessibility outcomes (new emphasis)
Outcome: TimingAdequate time (retained, broadened)
New structureOutcomes-based architecture (fundamental change)
174 outcomes174 outcomes (March 2026 draft count)

Scan your site against WCAG 3.0 (Draft)

No signup. 30 seconds.

Start with WCAG 2.2 AA today