WCAG 3.0 Working Draft Released March 2026: 174 New Outcomes and What They Mean

The most significant change in WCAG 3.0 is the complete replacement of the familiar conformance model:

WCAG 2.x Model (Current):
• Three conformance levels: A, AA, AAA
• Binary pass/fail for each success criterion
• 78 success criteria in WCAG 2.2
• Focus on individual page compliance

WCAG 3.0 Model (Proposed):
• No A/AA/AAA levels
• 174 outcomes organized by guidelines
• Outcomes can be tested with multiple methods
• Focus on user experience across the entire product
• Assertions and scoring replace binary pass/fail
• Covers websites, web apps, interactive components, media/VR, authoring tools, and testing tools

Why the Change:

The W3C AG Working Group recognized that the A/AA/AAA model has limitations:

• Binary pass/fail does not capture partial compliance or improvement
• Page-level testing misses application-level barriers
• Modern web apps (single-page apps, progressive web apps) do not fit the page model
• New interaction patterns (voice, gesture, VR) need broader coverage
• The checkbox approach encouraged minimal compliance rather than genuine accessibility

WCAG 3.0's 174 outcomes expand coverage beyond traditional web pages:

Categories Include:

• Perceivable: Text alternatives, time-based media, adaptable content, distinguishable presentation
• Operable: Keyboard access, timing, seizure prevention, navigation, input methods
• Understandable: Readable content, predictable behavior, input assistance
• Robust: Compatible with assistive technologies
• NEW: Interaction patterns — touch, gesture, voice, controller
• NEW: Immersive content — VR, AR, spatial computing
• NEW: Authoring tools — the tools that create content must produce accessible output
• NEW: Testing tools — accessibility testing tools themselves must be accessible

Key Structural Differences:

Each outcome in WCAG 3.0 has:
• Guidelines — high-level objectives
• Requirements — what must be met
• Assertions — testable claims about compliance
• Methods — specific ways to test (replaces the techniques documents)

This structure allows for more nuanced assessment than binary pass/fail, recognizing that accessibility is a spectrum rather than a checkbox.

| Milestone | Estimated Date | |-----------|---------------| | Working Draft (current) | March 2026 | | Additional Working Drafts | 2026-2027 | | Candidate Recommendation | Q4 2027 (projected) | | W3C Recommendation (final) | 2028-2030 | | Legal adoption (earliest) | 2030+ |

Why So Long:

• The AG Working Group must resolve the conformance model design
• 174 outcomes each need testable methods developed
• Public review and comment periods take 6-12 months each
• ISO standardization adds another 1-2 years
• Legal adoption requires new rulemaking (another multi-year process)

What This Means:

WCAG 2.1 AA (and increasingly 2.2 AA) will remain the legal standard for at least the next 4-5 years. Organizations investing in WCAG 2.1/2.2 compliance are NOT wasting money — this work will remain relevant and necessary well into the 2030s.

Strategic Recommendation:

1. Meet WCAG 2.1 AA for the April 2026 legal deadline 2. Audit for WCAG 2.2 gaps (nine additional criteria, mostly minor changes) 3. Monitor WCAG 3.0 development for long-term planning 4. Do NOT delay current compliance waiting for WCAG 3.0

While WCAG 3.0 is years away, WCAG 2.2 is available now and already being adopted:

• Published: October 5, 2023 (W3C Recommendation)
• ISO Standard: Approved as ISO/IEC 40500:2025 (October 2025)
• California: State agencies already required to meet WCAG 2.2 AA
• European Accessibility Act: References WCAG 2.2 (effective June 2025)
• Backward Compatible: Meeting WCAG 2.2 automatically satisfies 2.1

The 9 New Success Criteria in 2.2:

1. Focus Not Obscured (Minimum) — focused elements must be at least partially visible 2. Focus Not Obscured (Enhanced) — focused elements must be fully visible 3. Focus Appearance — visible focus indicators with minimum size 4. Dragging Movements — alternatives for drag-and-drop 5. Target Size (Minimum) — 24x24 CSS pixels for interactive targets 6. Consistent Help — help mechanisms in consistent locations 7. Redundant Entry — auto-populate previously entered information 8. Accessible Authentication (Minimum) — no cognitive function tests 9. Accessible Authentication (Enhanced) — extended authentication requirements

Practical Effort:

For most government websites already meeting WCAG 2.1 AA, the jump to 2.2 requires:

• Increasing button/link target sizes to 24px minimum (CSS change)
• Ensuring visible focus indicators (CSS change)
• Adding alternatives to CAPTCHAs (may require form changes)
• Ensuring help links appear consistently (usually already the case)

These are minor changes that future-proof your compliance posture.

For the full WCAG 2.2 analysis, see our WCAG 2.2 ISO Standard guide.