WCAG 3.0: What to Expect — The Complete 2026 Guide
WCAG 3.0 — codenamed "Silver" — is the most ambitious redesign of web accessibility standards in 25 years. It replaces pass/fail compliance with a scoring model, expands coverage to apps and emerging tech, and fundamentally rethinks how conformance is measured. Here's everything you need to know before it arrives.
WCAG 3.0 Is Still a Working Draft (June 2026)
WCAG 3.0 has not been finalized. No regulation currently requires WCAG 3.0 compliance. Your current ADA obligation is WCAG 2.1 Level AA. Read this as preparation for the future — not as current legal requirements.
📋 Table of Contents
1. What Is WCAG 3.0 and Why Does It Exist?
The Web Content Accessibility Guidelines (WCAG) have been the backbone of digital accessibility since WCAG 1.0 was published in 1999. WCAG 2.0 arrived in 2008, WCAG 2.1 in 2018, and WCAG 2.2 in 2023 — each adding new success criteria while preserving backward compatibility.
WCAG 3.0 is not an incremental update. It's a ground-up redesign developed by the W3C's Accessibility Guidelines Working Group (AGWG) under the project name "Silver." The impetus for WCAG 3.0 comes from growing frustration with the limitations of the 2.x framework:
- Binary pass/fail is too rigid: A website can "pass" every WCAG 2.2 AA criterion and still be genuinely difficult for users with disabilities to use. Conversely, one minor technical failure can cause a "violation" even when the site is largely accessible.
- The standard doesn't cover emerging technologies: Mobile apps, voice interfaces, VR/AR, augmented reality, and AI-generated content all present accessibility challenges that WCAG 2.x wasn't built to address.
- Testing is inconsistent: Two accessibility auditors testing the same page against WCAG 2.2 can reach different conclusions, because many criteria are ambiguous about what "passes."
- Small technical issues overshadow real outcomes: Legal standards focus on whether a success criterion is technically met, not whether users with disabilities can actually accomplish what they came to do.
WCAG 3.0 attempts to solve all of these problems with a completely different approach to accessibility conformance.
2. WCAG 3.0 Timeline: Where Are We Now?
W3C publishes the initial Silver requirements document. Early framework for outcomes-based testing introduced.
Formal WCAG 3.0 name adopted. Scoring model (0–4 scale) introduced. Bronze/Silver/Gold levels proposed.
Multiple Working Drafts refine the conformance model. W3C emphasizes WCAG 3.0 is still experimental — WCAG 2.x remains operative.
Significant restructuring of how Bronze conformance is defined. User research incorporated into outcome testing methods.
Core accessibility outcomes begin to stabilize. W3C expects to publish more complete drafts for broad review.
Still in active development. No publication target confirmed. WCAG 2.1/2.2 remain the legal and practical standard.
Most experts expect formal publication no earlier than 2027, with regulatory adoption following years later.
📌 Bottom Line on Timing
There is no confirmed publication date for WCAG 3.0. The W3C has explicitly warned against expecting a specific timeline. Treat WCAG 3.0 guidance as forward-looking context — not an imminent compliance deadline.
3. The 5 Biggest Changes in WCAG 3.0
Scoring Replaces Pass/Fail
High ImpactEach accessibility outcome in WCAG 3.0 is scored 0–4 rather than pass or fail. A score of 0 means the outcome is not met at all; 4 means it's met excellently with no barriers. Overall conformance is determined by combining scores across all tested outcomes.
Three Conformance Levels: Bronze, Silver, Gold
High ImpactA, AA, AAA levels are replaced by Bronze (foundational), Silver (comprehensive), and Gold (exceptional). Bronze roughly maps to current WCAG 2.x AA, but the conformance calculation is completely different.
Outcomes Replace Success Criteria
High Impact'Success criteria' — the binary rules in WCAG 2.x — become 'outcomes': user-centered goals like 'users can navigate using only a keyboard.' Each outcome has multiple testing methods, reducing auditor disagreement.
Expanded Scope Beyond Web Pages
Medium ImpactWCAG 3.0 is designed to cover web pages, mobile apps, software, VR/AR, voice interfaces, and AI-generated content — anything digital. This is a major expansion from WCAG 2.x's web-page focus.
User Testing as a Conformance Method
Medium ImpactSilver and Gold conformance can require actual testing with users with disabilities, not just automated checks and expert review. This makes higher conformance levels more rigorous and meaningful.
4. The New Scoring Model Explained
The scoring model is the most consequential change in WCAG 3.0. Under WCAG 2.x, each success criterion is either met or not. A single failure — even a minor one on a low-traffic page — can technically mean your site "doesn't conform" to WCAG 2.1 AA.
WCAG 3.0 replaces this with a 0–4 scoring scale:
The outcome is not being addressed at all. No effort to meet the accessibility need.
Some effort, but significant barriers remain. Most users with the relevant disability cannot complete the task.
Moderate accessibility. Many users can succeed, but barriers remain for some. Roughly comparable to failing WCAG 2.x.
The accessibility outcome is met. Users with the relevant disability can reliably accomplish the task. This is the Bronze conformance target.
Exceptional accessibility. Users with the relevant disability can not only complete the task but have a positive, optimized experience.
Bronze conformance requires all critical outcomes to score at least 3. The exact thresholds for Silver and Gold are still being finalized in the Working Draft.
Critically, WCAG 3.0 scores are weighted by the number of affected users — a barrier affecting screen reader users in a critical checkout flow weighs more heavily than an obscure interaction barrier in an edge-case scenario.
5. Bronze, Silver, and Gold Conformance Levels
Bronze
Roughly WCAG 2.x AA
- ✓All critical outcomes score ≥3
- ✓Automated testing methods passed
- ✓Expert review completed
- ✓No critical failures remaining
The baseline for legal compliance once adopted
Silver
Beyond current WCAG AA
- ✓All Bronze requirements met
- ✓User testing with disabled users
- ✓Extended outcome coverage
- ✓Documented remediation process
Recommended for high-traffic public services
Gold
Exceeds any current standard
- ✓All Silver requirements met
- ✓Broad user testing program
- ✓Proactive user feedback channels
- ✓Continuous accessibility monitoring
Reserved for exemplary accessible design
The Bronze level is most relevant for organizations currently focused on ADA compliance. It's designed to be achievable by any well-resourced team that takes accessibility seriously — similar to what achieving WCAG 2.1 AA represents today.
6. Outcomes vs. Success Criteria: A New Testing Paradigm
In WCAG 2.x, the unit of measurement is the "success criterion" — a specific, testable requirement like "1.1.1 Non-text Content: All non-text content that is presented to the user has a text alternative." Each criterion has a pass/fail result.
WCAG 3.0 replaces success criteria with "outcomes" — high-level accessibility goals expressed from the user's perspective. For example:
WCAG 2.x Success Criterion
All non-text content that is presented to the user has a text alternative that serves the equivalent purpose, except for the situations listed [exceptions follow].
WCAG 3.0 Outcome
Users who cannot perceive visual content can access equivalent information through alternative means, including text descriptions, audio descriptions, and structured data.
Each outcome has multiple methods for meeting it — specific technical tests, automated checks, and user testing procedures. This modularity means the standard can evolve as technology changes without requiring a complete rewrite of the guidelines themselves.
The methods approach also enables better tooling. Automated testing tools can be tied to specific methods, making it clearer what tools test and don't test. This is a significant improvement over the current situation where automated tools cover an estimated 30–40% of WCAG 2.x criteria.
7. Expanded Scope: Beyond Websites
WCAG 2.x was written for web pages and web applications. WCAG 3.0 is explicitly designed to cover:
This expanded scope is significant for organizations that build mobile apps, voice experiences, or AI-powered tools. Under current law, mobile app accessibility is addressed by the DOJ's interpretation of ADA Title III, but there are no specific technical standards. WCAG 3.0 would provide explicit guidance for the first time.
For AI-generated content specifically, WCAG 3.0 is working to address accessibility of outputs — ensuring that AI-generated images include alt text, AI-generated audio includes transcripts, and AI-generated interfaces are navigable. This is an area where WCAG 2.x offers no guidance.
8. WCAG 3.0 vs. WCAG 2.2: Side-by-Side Comparison
| Feature | WCAG 2.2 | WCAG 3.0 |
|---|---|---|
| Compliance model | Pass/fail per criterion | Scored 0–4 per outcome |
| Conformance levels | A, AA, AAA | Bronze, Silver, Gold |
| Unit of assessment | Success criteria (87 in WCAG 2.2) | Outcomes + methods |
| Scope | Web pages & web apps | Web, mobile, software, VR, AI, voice |
| User testing required | No (expert review sufficient) | Required for Silver and Gold |
| Legal status (US) | Referenced by DOJ, courts, regulations | Not yet adopted |
| Current status | Published W3C Recommendation (2023) | Working Draft — not finalized |
| Backward compatibility | Builds on WCAG 2.1 | New structure, WCAG 2.x concepts preserved |
| Key dates | Published Oct 2023 | No confirmed publication date |
9. How to Prepare Now Without Losing WCAG 2.x Compliance
You don't need to choose between WCAG 2.x compliance and WCAG 3.0 readiness. The standards are compatible — work done today to achieve genuine WCAG 2.1 AA compliance will position you well for WCAG 3.0 Bronze conformance.
What Transfers Directly
- Keyboard accessibility — WCAG 3.0 preserves keyboard navigation requirements
- Color contrast — WCAG 3.0's contrast requirements are similar to and likely stricter than WCAG 2.x
- Text alternatives for images — Alt text requirements are maintained
- Form labels and error messages — Core form accessibility carries forward
- Semantic HTML structure — Proper heading hierarchy and landmark regions remain important
- Captions for video — Video accessibility requirements are preserved and expanded
What to Start Building Now
- User testing program: WCAG 3.0 Silver and Gold require actual user testing with people with disabilities. Starting to build this capacity now prepares you for higher conformance levels.
- Accessibility statement and feedback mechanism: WCAG 3.0 is expected to require documented accessibility feedback channels. This is good practice regardless.
- Documented remediation process: Maintain records of accessibility issues found and fixed. This documentation will likely be required for Silver conformance.
- Mobile and app accessibility testing: WCAG 3.0's expanded scope means your app accessibility work will count alongside your web work.
✅ The Safest Path: Focus on WCAG 2.1 AA Now
WCAG 2.1 Level AA is your legal obligation today. WCAG 3.0 is not yet finalized and may still change significantly. Achieving genuine, well-documented WCAG 2.1 AA compliance is the best investment you can make — it protects you legally now and positions you for WCAG 3.0 Bronze in the future.
📊 Compare Accessibility Testing Tools
Whether you're targeting WCAG 2.2 today or preparing for WCAG 3.0 tomorrow, the right accessibility tools matter. See how leading platforms compare.
Compare Accessibility Tool Pricing →Sponsored
Audit your site's full technical health
SEMrush Site Audit checks 130+ issues — missing alt text, broken links, slow pages. Free crawl up to 100 pages, no credit card required.
10. Frequently Asked Questions
When will WCAG 3.0 be finalized?
There is no confirmed publication date. As of mid-2026, WCAG 3.0 is still a Working Draft undergoing significant development. Most accessibility experts estimate formal publication no earlier than 2027, with legal adoption following years after that. Do not plan your accessibility program around WCAG 3.0 timelines.
What is the biggest difference between WCAG 2.x and WCAG 3.0?
The shift from binary pass/fail to a 0–4 scoring model is the most fundamental change. A website that currently 'fails' WCAG 2.2 due to one issue might score a 3 out of 4 on the equivalent WCAG 3.0 outcome. This more nuanced measurement is designed to better reflect actual accessibility impact.
Do I still need to comply with WCAG 2.1 and 2.2?
Yes. ADA compliance is currently measured against WCAG 2.1 Level AA in most legal contexts. WCAG 2.2 is the current W3C Recommendation. WCAG 3.0 is not finalized and carries no legal weight. WCAG 2.1 AA compliance is your obligation today.
Will WCAG 3.0 be harder to meet than WCAG 2.2?
For Bronze conformance, the difficulty is roughly comparable to WCAG 2.2 AA. Silver and Gold are meaningfully harder, requiring user testing and comprehensive outcome coverage beyond current standards. However, the scoring model means a single minor issue won't cause a conformance failure.
How should I prepare for WCAG 3.0 today?
Focus on genuine WCAG 2.1 AA compliance — not just automated tool compliance, but real accessibility for users with disabilities. Build a documented accessibility testing program, create a user feedback mechanism for accessibility issues, and consider starting user testing with disabled users. This work will directly transfer to WCAG 3.0 Bronze conformance.
Is Your Website Ready for Today's Standards?
WCAG 3.0 is coming — but WCAG 2.1 AA is your obligation today. Run a free scan to find your current gaps before a plaintiff does.