WCAG 3.0
What's Coming & How to Prepare
W3C Accessibility Guidelines 3.0 is a major rework of WCAG: a broader scope and a new conformance model. It is still an incomplete working draft as of September 2026. Here's what you need to know.
Action right now: Focus on WCAG 2.2 AA: it includes every WCAG 2.0 and 2.1 AA criterion that today's laws reference. WCAG 3 has no set completion date and is expected to take several more years.
Standards Timeline
Final W3C Recommendation. Adds 9 new success criteria.
Incomplete draft: W3C is still developing the guidelines and a new conformance model.
Estimated timeline based on current W3C pace. Not yet confirmed.
Not yet a standard. Do NOT plan compliance requirements around this date.
What's Actually Changing in WCAG 3
Based on the September 2026 Working Draft. Details will change before the final standard.
Broader Scope
Web Content Accessibility Guidelines (web only)
W3C Accessibility Guidelines: covers web content, apps, tools, publishing and emerging technologies
New Conformance Model
Binary pass/fail per success criterion at Level A, AA, or AAA
To conform, content must meet all core requirements. Core requirements are tagged by their impact on people (physical harm, risk, barrier or friction), and results are reported in six tiers; tier 3 means every core requirement is met.
Outcomes and Requirements
Success criteria written as testable technical requirements
Guidelines written as outcome statements, each with core and supplemental requirements, assertions and recommended practices. Methods, similar to WCAG 2 Techniques, are published separately.
Contrast Algorithm
WCAG 2.x algorithm: minimum 4.5:1 ratio for text (known to have flaws with dark colors)
To be decided. APCA was removed from the WCAG 3 working draft in July 2023, and the contrast method is still being developed.
How to Prepare Now
Actions you can take today that will serve you under WCAG 2.x AND position you well for WCAG 3.
Achieve WCAG 2.2 AA Now
CriticalWCAG 2.2 is the current W3C Recommendation. Laws often reference earlier versions (Section 508: WCAG 2.0; ADA Title II and EN 301 549: WCAG 2.1), and meeting WCAG 2.2 AA also meets those. Start here; don't wait for WCAG 3.
Run a WCAG 2.2 scanFocus on Real Outcomes for Users
HighWCAG 3 emphasizes real user outcomes. Ask whether your product actually works for people with disabilities, as well as whether it passes automated checks.
Learn about user testingImplement Cognitive Accessibility
HighWCAG 3 will significantly expand cognitive accessibility requirements. Start implementing W3C COGA guidelines now to be ahead of the standard.
Read Cognitive GuideBuild Accessible Design Systems
MediumWCAG 3 will apply to software and native apps. If you build design systems, ensure they support AT from the ground up rather than retrofitting accessibility.
View ARIA PatternsMonitor the W3C WCAG 3 Working Group
LowWCAG 3 is actively being developed. Subscribe to the WAI announcements newsletter to stay current as the draft evolves.
W3C WAI Website (opens in new tab)Common WCAG 3 Myths, Debunked
I should wait for WCAG 3 before fixing accessibility
WCAG 3 is years away from being a final standard. Laws reference WCAG 2 today (Section 508: 2.0; ADA Title II and EN 301 549: 2.1), and WCAG 2.2 AA includes all of those, so waiting has no upside.
WCAG 2.x will become obsolete when WCAG 3 arrives
WCAG 2.x will remain legally valid for many years after WCAG 3 is published. International laws take years to update their references. You will not need to start over.
WCAG 3 will make current work pointless
Most accessibility fundamentals (keyboard navigation, screen reader support, contrast, alt text) carry forward unchanged. WCAG 3 widens the scope; it does not invalidate existing work.
APCA will replace WCAG 2.x contrast requirements
APCA was removed from the WCAG 3 working draft in July 2023. As of 2026 the WCAG 3 contrast algorithm is officially 'yet to be determined.' Do not implement APCA as a compliance requirement.
Start With What's Required Today
WCAG 2.2 AA is the version to build to now: meeting it also meets the earlier versions that laws reference. Get there today and you'll be well placed for WCAG 3 when it arrives.