WCAG 3.0 is coming, and it changes nearly everything about how we measure accessibility. The binary pass-fail system that has defined web accessibility since 2008 is being replaced by a graduated scoring model. The familiar A, AA, and AAA conformance levels become Bronze, Silver, and Gold. Success criteria become outcomes, and there are 174 of them in the latest draft compared to 86 in WCAG 2.2. The scope expands from web content to mobile apps, PDFs, VR, voice interfaces, and IoT devices. Even the name changes: WCAG no longer stands for Web Content Accessibility Guidelines but W3C Accessibility Guidelines, reflecting the broader scope. The W3C published the latest Working Draft in September 2025, with a Candidate Recommendation expected around late 2027 and final publication targeted for late 2029. No law anywhere in the world currently references WCAG 3.0, and WCAG 2.x will not be deprecated for several years after 3.0 is finalized. But the philosophy behind WCAG 3.0 is already influencing how accessibility professionals think and work. This guide covers what is changing, what is staying the same, and what you should do now to be ready.
WCAG 3.0 at a Glance
The Current Status of WCAG 3.0
WCAG 3.0 is still a Working Draft, which means it is an official work in progress but not yet a finished standard. The W3C describes it as an incomplete draft in an exploratory or developing phase that will change substantially before finalization.
The most recent public Working Draft was published on September 4, 2025, introducing 174 outcomes. A subsequent Editor's Draft from January 2026 restructured the guidelines into a hierarchy of guidelines, requirements, assertions, and methods. The W3C Accessibility Guidelines Working Group plans to publish a detailed timeline in April 2026.
The realistic timeline based on W3C statements and expert analysis looks like this: a Candidate Recommendation around late 2027, a final major draft for public comment in late 2027 or early 2028, and a target for W3C Recommendation status in late 2029. As Deque's accessibility team points out, WCAG 2.0 took seven years from initial criteria listing to completion, and WCAG 3.0 may follow a similar trajectory, meaning finalization might not happen before 2030.
This matters because the gap between now and finalization is your preparation window. Organizations that start adapting now will transition smoothly. Those that wait for the final standard will face a scramble.
What Is Actually Changing
WCAG 3.0 is not a minor update. It is a fundamental rethinking of how accessibility is measured and evaluated. Here are the major shifts.
From Pass-Fail to Graduated Scoring
Under WCAG 2.x, each success criterion either passes or fails. There is no middle ground. A website with one missing alt text on a decorative image and a website with every single image lacking alt text both fail the same criterion in the same way.
WCAG 3.0 introduces a 0 to 4 scoring scale for each outcome. A score of 0 means very poor, with a critical error or less than 60 percent compliance. A score of 1 means poor, at 60 to 69 percent compliance. A score of 2 means fair, at 70 to 79 percent. A score of 3 means good, at 80 to 94 percent. A score of 4 means excellent, at 95 to 100 percent with no critical errors.
This graduated approach recognizes that accessibility is a spectrum, not a binary state. A site with 96 percent of images having good alt text scores a 4, while a site with only 72 percent coverage scores a 2. Both have room for improvement, but they are not treated as equivalent failures. This makes prioritization clearer and progress more measurable.
From A-AA-AAA to Bronze-Silver-Gold
The familiar three-tier conformance system is being replaced. Bronze is the minimum conformance level, roughly equivalent to current WCAG 2.2 Level AA. It requires an average score of at least 3.5 across all outcomes and at least 3.5 in every functional category such as vision, hearing, cognition, and mobility. Zero critical errors are permitted.
Silver requires higher scores, broader coverage, and usability validation from people with disabilities. It introduces Supplemental Requirements and Assertions.
Gold represents exemplary accessibility. It requires advanced usability testing, inclusive research, user testing with diverse disability groups, and documented organizational processes.
A critical new concept is functional categories. Instead of evaluating conformance across all criteria equally, WCAG 3.0 groups outcomes by the disability types they address. Each functional category must independently meet the minimum threshold. You cannot compensate for poor cognitive accessibility scores with excellent vision accessibility scores.
From Success Criteria to Outcomes
WCAG 2.2 has 86 success criteria that describe technical requirements. WCAG 3.0 replaces these with 174 outcomes that describe measurable user needs. The shift is from does this element meet a technical criterion to can the user actually complete their task.
Outcomes are user-centered statements. Instead of images of text should not be used, an outcome might state users can access all information presented in images through text alternatives. The distinction matters because it focuses testing on real user impact rather than technical compliance.
The September 2025 draft's 174 outcomes will likely be refined and some dropped during the development process. But the move from technical criteria to user-centered outcomes is the philosophical core of WCAG 3.0 and will not change.
Critical Errors: The Automatic Fail
WCAG 3.0 introduces the concept of critical errors, which are high-impact failures that directly block task completion. Examples include content that flashes in ways that could cause seizures, keyboard traps that prevent navigation, auto-playing audio with no way to pause, and submit buttons that cannot be reached via keyboard.
A single critical error results in the lowest possible score for that outcome, regardless of how well everything else performs. This prevents organizations from achieving Bronze conformance while having a fundamental barrier that completely blocks some users. It is a sensible safeguard that WCAG 2.x lacked.
Assertions: Documenting Your Process
WCAG 3.0 introduces Assertions as a new concept. These are documented, attributable claims about an organization's accessibility processes. Examples include statements that usability testing was conducted with users with disabilities, that staff received accessibility training, that plain language evaluations were performed, and that assistive technology testing was conducted.
Assertions must include a process statement, date, scope, contact information, and supporting requirements. They complement the technical requirements but cannot substitute for them. An organization cannot claim Silver by having great processes while the website itself has significant accessibility barriers.
This is significant because it formalizes something the accessibility community has long advocated: accessibility is an ongoing organizational commitment, not a one-time technical checkbox.
Expanded Scope Beyond Web Content
The name change from Web Content Accessibility Guidelines to W3C Accessibility Guidelines signals a major expansion in scope. WCAG 3.0 explicitly covers mobile applications, PDFs and ePub documents, VR and AR environments, voice interfaces, IoT devices, and authoring and testing tools.
New areas of particular note include cognitive accessibility, with guidelines specifically for users with cognitive, attention, and learning disabilities. The single idea outcome requires text segments to present one concept each, benefiting users with short-term memory challenges. There are requirements for explaining non-literal language such as idioms and metaphors, which helps non-native speakers and autistic users.
Privacy gets attention for the first time in an accessibility standard. WCAG 3.0 includes outcomes around disability information privacy, preventing disclosure of disability-related data to third parties and AI algorithms. This recognizes that disability needs, preferences, and assistive technology usage are sensitive personal information.
Non-verbal communication is addressed through outcomes for understanding tone of voice, facial expressions, and emotionally meaningful audio in media content, supporting users on the autism spectrum who have difficulty interpreting social cues.
Will WCAG 3.0 Replace WCAG 2.2
No, at least not for a long time. The W3C has stated explicitly that WCAG 3 will not supersede WCAG 2, and WCAG 2 will not be deprecated for at least several years after WCAG 3 is finalized.
WCAG 2.x is embedded in laws and regulations worldwide. The European Accessibility Act references EN 301 549, which incorporates WCAG 2.1 Level AA. The US DOJ's ADA Title II rule references WCAG 2.1. Section 508 currently references WCAG 2.0. None of these will switch to WCAG 3.0 until years after it becomes a Recommendation, and even then the transition will be gradual.
Practically, this means organizations will run on WCAG 2.2 AA for current legal compliance while gradually incorporating WCAG 3.0 practices. The two standards will coexist for at minimum several years after WCAG 3.0 finalization, meaning WCAG 2.x will likely remain legally relevant through at least 2032 to 2035.
The bottom line: achieving solid WCAG 2.2 AA compliance today is the single best preparation for WCAG 3.0. Bronze level aligns closely with WCAG 2.2 AA. Everything you build on that foundation positions you well for the transition.
How WCAG 3.0 Changes Testing
Current automated accessibility testing tools catch approximately 30 to 40 percent of WCAG issues. Manual testing covers the rest. WCAG 3.0 changes the testing landscape in several ways.
Scoring replaces binary results. Tools will need to calculate percentage-based scores per outcome rather than simple pass or fail determinations. An image alt text audit will need to report what percentage of images have good alternatives, not just whether any are missing.
Two test categories emerge: quantifiable tests with high consistency between testers, and qualitative tests that rely on evaluator judgment. Both contribute to the final score.
Testing must cover complete task flows, not just individual page elements. Can a user find a product, add it to cart, and complete checkout? That end-to-end test matters more than whether a single button meets a contrast ratio.
For SaaS accessibility checking tools, this represents an opportunity. The shift toward graduated scoring aligns naturally with dashboards that show progress over time rather than binary compliance badges. Tools that adopt outcome-based reporting early will be ahead of the market when WCAG 3.0 becomes the standard.
What You Should Do Now
You do not need to wait for WCAG 3.0 to be finalized to start preparing. Here are concrete actions organized by timeline.
Immediate Actions for 2026
Achieve solid WCAG 2.2 AA compliance. This is repeated by virtually every accessibility expert because it is the single most effective preparation. Bronze level aligns closely with WCAG 2.2 AA, so everything you do to meet 2.2 AA positions you for 3.0 Bronze.
Audit your current state across all digital touchpoints: websites, mobile apps, PDFs, videos, and forms. Use a combination of automated scanning and manual testing. Our free accessibility checker at web-accessibility-checker.com gives you an instant WCAG 2.2 report to identify your baseline.
Start user testing with people with disabilities. WCAG 3.0's Silver and Gold levels rely heavily on evidence from real user journeys. Begin collecting that data now. Even informal testing sessions provide valuable insights that pure technical audits miss.
Document your accessibility processes. WCAG 3.0's Assertions model rewards organizations that can demonstrate training records, testing methodologies, and remediation workflows. Start building that documentation now.
Short-Term Steps for 2026 to 2027
Address cognitive accessibility gaps. Review your content for plain language, clear navigation, consistent patterns, and support for users with cognitive and learning disabilities. This is one of the biggest expansion areas in WCAG 3.0 and one where most websites have significant room for improvement.
Adopt task-flow thinking in your testing. Instead of testing individual pages in isolation, test complete user journeys from start to finish. Can someone register an account, find what they need, and complete a transaction without hitting an accessibility barrier at any step?
Create an accessibility design system with built-in accessible components. When accessibility is baked into your component library, every page built from those components starts with a strong foundation.
Monitor WCAG 3.0 drafts as they evolve. The Working Drafts are publicly available at the W3C website. You can participate in public comment periods through the W3C's GitHub repository for WCAG 3.0.
Medium-Term Preparation for 2027 to 2029
Pilot WCAG 3.0 scoring internally. Apply the 0 to 4 outcome scoring model to your existing accessibility data to understand where your organization falls on the new scale. This gives you early insight into which functional categories need the most attention.
Establish severity and impact tracking. Instead of counting accessibility violations, measure their impact on real user tasks. This aligns with the outcome-based philosophy of WCAG 3.0 and produces more actionable remediation priorities.
If you are building VR experiences, voice interfaces, IoT products, or other emerging technology, start considering accessibility from the design phase. WCAG 3.0 brings these under the accessibility umbrella for the first time, and retrofitting accessibility into these platforms is significantly harder than designing it in.
How WCAG 3.0 Affects Legal Compliance
As of February 2026, no law or regulation anywhere in the world references WCAG 3.0. The legal landscape is anchored firmly in WCAG 2.x.
The European Accessibility Act references EN 301 549, which incorporates WCAG 2.1 Level AA. EN 301 549 is being revised and may adopt WCAG 2.2, but not WCAG 3.0. The US ADA Title II rule references WCAG 2.1. Section 508 references WCAG 2.0 and a refresh to 2.1 or 2.2 is under discussion.
Even after WCAG 3.0 is finalized around 2029 to 2030, regulatory adoption would take additional years. Laws typically reference stable, finalized W3C Recommendations, and regulatory update cycles add further delay. A realistic timeline for WCAG 3.0 appearing in law is not before 2031 to 2035 at the earliest.
This means your compliance obligation for the next several years is WCAG 2.2 AA. However, early adoption of WCAG 3.0 concepts such as usability testing, cognitive accessibility, and outcome-based evaluation strengthens your legal defense under existing laws. Demonstrating genuine user-centered accessibility work is always viewed favorably, regardless of which specific standard version a law references.