Key Takeaways
- 1WCAG 3.0 won't be finalized until 2028 at the earliest — a January 2026 Working Draft exists, with Candidate Recommendation targeted for Q4 2027
- 2The name changes from "Web Content" to "W3C" Accessibility Guidelines — reflecting expanded scope beyond websites to mobile apps, VR/XR, operating systems, and authoring tools
- 3Pass/fail conformance is being replaced with foundational requirements, supplemental requirements, and assertions — potentially enabling tiered conformance levels (bronze, silver, gold)
- 4Cognitive accessibility gets major attention — guidelines for clear language, consistent navigation, and reducing cognitive load address gaps in WCAG 2.x
- 5Your priority today is still WCAG 2.1 AA — this is what ADA Title II, the European Accessibility Act, and Canada's ACA all require
1. What Is WCAG 3.0?
WCAG 3.0 is the next generation of accessibility standards from the World Wide Web Consortium (W3C). It is being developed by the Accessibility Guidelines Working Group (AG WG), the same body that created WCAG 2.0, 2.1, and 2.2.
The most immediately noticeable change? The name itself. In WCAG 3.0, "WCAG" stands for "W3C Accessibility Guidelines" instead of "Web Content Accessibility Guidelines." This isn't just rebranding — it signals a fundamental expansion. WCAG 3.0 aims to cover everything digital: websites, mobile applications, virtual reality environments, digital documents, authoring tools, user agents (browsers), and even operating systems.
The project was originally codenamed "Silver" (from Ag, the chemical symbol for silver — a reference to the AG Working Group). While you may still see "Silver" referenced in older documentation, the official name is now WCAG 3.0.
WCAG 3.0 has been in development since 2016, with the first Working Draft published in January 2021. The most recent Working Draft was published in September 2025, with a substantially complete draft published in early 2026. It remains a work in progress, and significant changes are still expected before finalization.
2. Why Is WCAG 3.0 Being Developed?
WCAG 2.0 was published in 2008. While updates (2.1 in 2018, 2.2 in 2023) added new success criteria, the fundamental structure has remained largely unchanged for nearly two decades. Several limitations have become increasingly apparent:
The Binary Problem
WCAG 2.x conformance is all-or-nothing. A website either conforms to Level AA or it doesn't — there's no credit for being 95% compliant. This discourages organizations that are making genuine progress but haven't reached full conformance. A site with one failing criterion is technically non-compliant, even if it's vastly more accessible than competitors.
Limited Cognitive Coverage
WCAG 2.x was designed primarily around sensory and motor disabilities — screen reader users, keyboard-only navigation, color contrast, audio descriptions. Cognitive disabilities — affecting comprehension, memory, attention, and language processing — were underserved. Given that cognitive disabilities are among the most common worldwide, this is a significant gap.
Technology Has Outpaced the Standard
When WCAG 2.0 was written, the iPhone was one year old. There was no VR, no single-page applications, no voice assistants, no AI-generated content. The "page" model that WCAG 2.x is built around doesn't map cleanly to modern web applications, mobile experiences, or immersive technologies.
Slow Update Cycle
The WCAG 2.x revision process takes years. From 2.0 (2008) to 2.1 (2018) was a decade. From 2.1 to 2.2 (2023) was five years. The web evolves faster than the standard can keep up. WCAG 3.0 is designed with a modular architecture that allows individual guidelines to be updated independently, enabling more rapid iteration.
Fragmented Standards Landscape
Currently, different aspects of accessibility are covered by separate standards: WCAG for web content, ATAG (Authoring Tool Accessibility Guidelines) for content creation tools, UAAG (User Agent Accessibility Guidelines) for browsers, and MWBP (Mobile Web Best Practices) for mobile. WCAG 3.0 aims to harmonize these into a single, comprehensive framework.
3. Key Changes from WCAG 2.x
WCAG 3.0 isn't an incremental update — it's a ground-up reimagining. Here are the most significant structural changes:
New Document Structure
WCAG 2.x organized requirements as Principles → Guidelines → Success Criteria → Techniques. WCAG 3.0 introduces a flatter structure with Guidelines containing Outcomes, which are then tested through Methods. This makes individual guidelines more self-contained and easier to update independently.
Graduated Conformance
Instead of A/AA/AAA levels, WCAG 3.0 introduces a tiered system with foundational requirements (baseline), supplemental requirements (going beyond), and assertions (organizational commitments). This could enable bronze/silver/gold conformance levels, rewarding organizations that invest in accessibility beyond the minimum.
Technology-Agnostic Design
WCAG 2.x requirements are written around web technologies (HTML, CSS, JavaScript). WCAG 3.0 guidelines are designed to be technology-agnostic, with platform-specific methods provided separately. This means the same accessibility principle can apply to a website, a mobile app, or a VR environment — with appropriate testing methods for each.
Modular and Iterative
The AG Working Group is following an agile development approach. Individual guidelines will reach maturity at different rates and can be published independently. This means WCAG 3.0 won't arrive as a single monolithic document — mature guidelines may be available for use before the entire standard is finalized.
4. The New Conformance Model
Perhaps the most impactful change in WCAG 3.0 is how conformance is measured. The binary pass/fail model of WCAG 2.x is being replaced with a three-layer system:
Layer 1: Foundational Requirements
These are the baseline — the minimum bar that all content must meet. Meeting all foundational requirements is intended to be broadly equivalent to WCAG 2.2 Level AA. These are non-negotiable accessibility requirements like providing text alternatives for images, ensuring keyboard accessibility, and maintaining sufficient color contrast.
Layer 2: Supplemental Requirements
These go beyond the baseline to demonstrate deeper accessibility commitment. Meeting supplemental requirements shows an organization has invested in accessibility beyond minimum compliance. This could include enhanced cognitive accessibility support, improved personalization options, or advanced assistive technology compatibility.
Layer 3: Assertions
This is entirely new. Assertions evaluate an organization's processes and culture around accessibility — not just the technical state of their content. Examples include having an accessibility policy, training staff on accessibility, including people with disabilities in user testing, and maintaining a remediation workflow. This recognizes that sustainable accessibility requires organizational commitment, not just passing technical checks.
This three-layer model enables what the W3C describes as tiered conformance. While the specific levels haven't been finalized, the working concept includes:
- Bronze: All foundational requirements met
- Silver: Foundational + supplemental requirements met
- Gold: Foundational + supplemental requirements + assertions satisfied
This is a significant philosophical shift. Instead of asking "is this website compliant?" the model asks "how committed is this organization to accessibility?" It rewards continuous improvement rather than one-time audits.
5. Expanded Scope: Beyond Web Content
The scope expansion is dramatic. While WCAG 2.x applied primarily to web pages, WCAG 3.0 aims to provide guidance for:
Websites & Web Apps
Traditional web content, single-page applications, progressive web apps
Mobile Applications
Native iOS and Android apps, hybrid apps, mobile-specific interactions
VR / XR / AR
Virtual reality, extended reality, 360° environments, spatial interfaces
Digital Documents
PDFs, Office documents, presentations, e-books
Authoring Tools
CMS platforms (WordPress, Drupal), design tools, content editors
User Agents & OS
Browsers, assistive technologies, operating systems, media players
For organizations, this means the same accessibility standard will eventually apply across all your digital products — not just your website. If you build mobile apps, create digital documents, or use VR in training, WCAG 3.0 will have specific guidance for each.
The scope expansion also means WCAG 3.0 effectively absorbs the guidance previously covered by ATAG (for authoring tools) and UAAG (for user agents), creating a single reference point instead of separate standards.
6. Cognitive Accessibility at Last
One of the strongest motivations for WCAG 3.0 is to properly address cognitive, learning, and neurological disabilities — an area where WCAG 2.x has been widely criticized as insufficient.
Cognitive disabilities are among the most common worldwide. They include conditions like autism spectrum disorder, ADHD, dyslexia, dyscalculia, intellectual disabilities, traumatic brain injury, and age-related cognitive decline. Yet WCAG 2.2's success criteria predominantly focus on sensory (visual, auditory) and motor (keyboard, touch) accessibility.
WCAG 3.0 includes emerging requirements that specifically address cognitive needs:
- →Clear Language: Explanations or unambiguous alternatives must be available for non-literal language such as idioms, metaphors, and jargon. For example, the idiom "Don't count your chickens before they hatch" would need an alternative explanation for users who process language literally.
- →Consistent Navigation: Interfaces should maintain predictable patterns and avoid unexpected changes that can disorient users with cognitive disabilities.
- →Reduced Cognitive Load: Content and interfaces should minimize the amount of information users need to hold in working memory to complete tasks.
- →Captions in 360° Environments: In immersive digital environments (like VR), captions must remain positioned directly in front of the user — a requirement that has no equivalent in WCAG 2.x.
- →Personalization Support: Content should support user preferences for text size, color schemes, information density, and interaction patterns to accommodate diverse cognitive needs.
This expanded cognitive coverage is long overdue. While WCAG 2.2 added a few criteria relevant to cognitive accessibility (like Focus Not Obscured and Consistent Help), WCAG 3.0 makes it a central pillar of the standard rather than an afterthought.
7. Views and Processes: Replacing the Page Model
WCAG 2.x is built around the concept of a "web page" — a resource identified by a URI. But modern digital experiences don't always map to discrete pages. Single-page applications dynamically update content without changing the URL. Mobile apps have screens, not pages. VR environments have scenes, not pages.
WCAG 3.0 introduces two new concepts to replace the page model:
Views
A view is content that is actively available — it can be read and interacted with — in the viewport at a given moment. By this definition, a modal dialog is a separate view from the page behind it, because the background content is not available while the modal is displayed.
This concept works across platforms: a web page is a view, a mobile app screen is a view, a VR scene is a view, and a dialog overlay is a view.
Processes
A process is a series of views that a user progresses through to complete a task, often in a specific order. Examples include checkout flows, form wizards, account registration, or booking sequences. Critically, processes can span multiple sites or applications — acknowledging that modern user journeys often cross platform boundaries (e.g., clicking a link in email, landing on a website, completing payment through a third-party processor).
This shift has practical implications for accessibility testing. Instead of auditing individual pages against a checklist, organizations will evaluate user journeys — end-to-end processes that real users actually perform. This is arguably more meaningful: a checkout flow where each individual page is technically compliant but the overall process is inaccessible wouldn't pass under WCAG 3.0.
8. WCAG 3.0 Timeline and Release Date
WCAG 3.0 has been in development for about a decade. Here's the current timeline based on the AG Working Group's published plans:
January 2021 — First Working Draft
Initial public draft establishing the new structure and direction. Heavily experimental.
June 2021 – September 2025 — Revised Working Drafts
Multiple iterations. Significant experimentation with conformance models, guideline structure, and testing methods.
January 2026 — Substantially Complete Draft ← We Are Here
A "fairly complete initial draft" per AG WG chair Rachael Bradley Montgomery. Open for public comment and review.
April 2026 — Projected Timeline Published
The AG WG plans to publish a detailed WCAG 3.0 timeline by this date.
Q4 2027 — Candidate Recommendation (Target)
The final stage before W3C Recommendation. Still subject to significant changes based on implementation experience.
2028+ — W3C Recommendation (Earliest)
The official, endorsed standard. Could slip further depending on implementation feedback and Working Group capacity.
⚠️ Important context: The W3C process inherently involves delays. WCAG 2.2 was originally expected in 2021 but wasn't published until October 2023. The 2028 target for WCAG 3.0 is ambitious. Many accessibility professionals expect the final standard in 2029 or later.
9. WCAG 3.0 vs. WCAG 2.2: Side-by-Side Comparison
One critical thing to understand: WCAG 2.2 will not be deprecated when WCAG 3.0 is published. Both standards will coexist. WCAG 2.2 is already embedded in legislation worldwide — the ADA Title II rule specifically references WCAG 2.1, the European Accessibility Act uses EN 301 549 (which maps to WCAG 2.1 AA), and Canada's ACA uses CAN/ASC-EN 301 549. Replacing these legislative references with WCAG 3.0 will take years of rulemaking.
10. Legal and Regulatory Impact
A common question: "Will I need to comply with WCAG 3.0?" The short answer: not yet, and not for years.
Currently, no legislation anywhere in the world references WCAG 3.0. The legal landscape is built on WCAG 2.1 (and increasingly 2.2):
- 🇺🇸United States: ADA Title II requires WCAG 2.1 Level AA (deadline April 24, 2026 for large entities). Title III relies on WCAG 2.0/2.1 AA as a benchmark in court settlements. Section 508 references WCAG 2.0 AA (with updates expected).
- 🇪🇺European Union: The European Accessibility Act (enforced since June 2025) uses EN 301 549, which harmonizes with WCAG 2.1 AA for web content.
- 🇨🇦Canada: The Accessible Canada Act uses CAN/ASC-EN 301 549 (adopted May 2024), aligning with WCAG 2.1 AA. Deadlines run from 2027 to 2028.
Even after WCAG 3.0 is finalized (2028+), it will take additional years for legislatures and regulatory agencies to update their references. The DOJ's ADA Title II rulemaking process took over a decade. Realistically, WCAG 3.0 won't appear in binding legislation until 2030 at the earliest.
However, organizations that proactively adopt WCAG 3.0 principles — especially cognitive accessibility and process-based evaluation — will be better positioned when the legal landscape inevitably shifts. Courts and settlement agreements could begin referencing WCAG 3.0 concepts even before formal legislative adoption.
11. How to Prepare Your Business
WCAG 3.0 isn't actionable yet — but here's how to position your organization for a smooth transition when it arrives:
Step 1: Achieve WCAG 2.1 AA Compliance First
This is your immediate legal obligation and the best foundation for WCAG 3.0. The foundational requirements in WCAG 3.0 are designed to be roughly equivalent to WCAG 2.2 Level AA. If you're compliant with 2.1 AA, you're already most of the way there.
Key deadlines: ADA Title II (April 24, 2026 for 50K+ entities), EAA (already in effect), Canada ACA (2027-2028). Don't wait for WCAG 3.0 — the current standard is what you'll be measured against.
Step 2: Build Accessibility Into Your Process
WCAG 3.0's assertion layer will evaluate your processes, not just your output. Start building accessibility into your development and content creation workflows now:
- Establish an accessibility policy
- Train developers, designers, and content creators
- Include accessibility in QA and code review
- Use automated testing in your CI/CD pipeline
- Include users with disabilities in usability testing
Step 3: Start Addressing Cognitive Accessibility
Even though cognitive accessibility requirements aren't fully codified yet, you can start making improvements:
- Use plain language and avoid unnecessary jargon
- Provide clear, consistent navigation across your site
- Break complex tasks into manageable steps
- Avoid unexpected changes in context
- Provide alternatives for figurative or idiomatic language
- Minimize the cognitive load of forms and interactive elements
Step 4: Think Beyond Your Website
If you have mobile apps, digital documents, or other non-web digital products, start evaluating their accessibility now. WCAG 3.0 will cover all of these, and many already fall under existing legal requirements (ADA Title II explicitly covers mobile apps; the EAA covers self-service terminals and e-commerce apps).
Step 5: Monitor and Maintain Continuously
WCAG 3.0's conformance model emphasizes ongoing commitment over point-in-time audits. The days of "get an accessibility audit, fix the issues, move on" are ending. Continuous monitoring catches regressions, tracks progress, and demonstrates the kind of sustained commitment that WCAG 3.0's assertion layer will eventually measure.
12. Frequently Asked Questions
When will WCAG 3.0 be released?
A substantially complete Working Draft was published in January 2026. Candidate Recommendation is targeted for Q4 2027, with the final W3C Recommendation (the official standard) not expected before 2028. Given historical delays (WCAG 2.2 was two years late), 2029 or later is realistic.
Will WCAG 3.0 replace WCAG 2.2?
Not immediately. WCAG 2.2 is embedded in legislation worldwide and will remain valid for years after WCAG 3.0 is published. Both standards will coexist, allowing a gradual transition. Think of it like HTML4 and HTML5 — there was a long overlap period.
What does WCAG stand for in version 3.0?
In WCAG 3.0, WCAG stands for "W3C Accessibility Guidelines" instead of "Web Content Accessibility Guidelines." This reflects the expanded scope beyond web content to mobile apps, VR/XR, authoring tools, user agents, operating systems, and digital documents.
Do I need to comply with WCAG 3.0 now?
No. WCAG 3.0 is still in development and no legislation requires it. Your immediate obligation is WCAG 2.1 Level AA under ADA Title II (deadline April 24, 2026), the European Accessibility Act (already in effect), and Canada's Accessible Canada Act (2027-2028 deadlines). Meeting WCAG 2.1 AA now is the best preparation for WCAG 3.0.
Will WCAG 3.0 address cognitive disabilities?
Yes — this is one of the primary motivations for the new standard. WCAG 3.0 includes requirements for clear language, consistent navigation, reduced cognitive load, and personalization. This addresses a significant gap in WCAG 2.x, which focused primarily on sensory and motor disabilities.
How should I prepare?
Focus on WCAG 2.1 AA compliance first. Beyond that: build accessibility into your development process (not just audits), start addressing cognitive accessibility, ensure mobile and app experiences are accessible, and use continuous monitoring to maintain compliance. All of these align with where WCAG 3.0 is heading.
What are WCAG 3.0 assertions?
Assertions are a new concept that evaluate organizational processes and culture around accessibility — not just technical compliance. They could include having an accessibility policy, training staff, including people with disabilities in testing, and maintaining remediation workflows. This recognizes that sustainable accessibility requires organizational commitment beyond passing technical checks.
What testing tools support WCAG 3.0?
Since WCAG 3.0 is still in development, no testing tools fully support it yet. Current tools like axe-core, WAVE, Lighthouse, and Pa11y test against WCAG 2.x criteria. As WCAG 3.0 methods are finalized, tools will be updated. Organizations like Deque (axe) and WebAIM (WAVE) are actively involved in the WCAG 3.0 development process.
The Bottom Line
WCAG 3.0 represents the biggest evolution in accessibility standards since WCAG 2.0 launched in 2008. The expanded scope, graduated conformance model, and cognitive accessibility focus will fundamentally change how organizations approach digital accessibility.
But it's years away from being legally required. Your priority today is WCAG 2.1 Level AA — the standard that ADA Title II, the European Accessibility Act, and Canada's Accessible Canada Act all mandate. Meeting that standard is both your legal obligation and the strongest foundation for WCAG 3.0 when it arrives.
The organizations that will transition most smoothly to WCAG 3.0 are the ones already treating accessibility as a continuous practice — not a one-time audit. That means building it into your development process, monitoring continuously, and addressing cognitive accessibility even before it's required.
Related Articles
WCAG 2.1 vs 2.2: What Changed and Why It Matters
Complete comparison of the two current standards
ADA Title II April 2026 Deadline Countdown
What public entities need to know before April 24
Section 508 Compliance: The Complete Guide for 2026
Federal accessibility requirements and how to meet them
Best Accessibility Testing Tools Compared (2026)
12 tools reviewed for automated and manual testing
Sources
- AbilityNet — "WCAG 3.0 Overview and Update 2026" (February 2026)
- Knowbility — "Be a Digital Ally: WCAG 3 Status and Review" — Rachael Bradley Montgomery (2025)
- W3C Accessibility Guidelines Working Group — "WCAG 3 Timeline"
- W3C — "Web Content Accessibility Guidelines (WCAG) 2.1" (June 2018)
- ADA.gov — "Fact Sheet: New Rule on the Accessibility of Web Content and Mobile Apps" (March 2024)