Accessibility standards are evolving, and the recently released WCAG 3.0 draft marks one of the most significant shifts in how digital accessibility may be defined and measured in the future. Unlike previous updates in the WCAG 2.x series, WCAG 3.0 proposes a fundamentally new framework, moving beyond strict technical checklists toward a more flexible, user-centered approach that emphasizes real-world usability and inclusive experiences.
To better understand what these changes could mean for organizations working toward accessible digital products, we spoke with Anitta Mary John, an IAAP-WAS (Web Accessibility Specialist) certified accessibility professional with over a decade of experience in the field. Anitta has worked extensively in accessibility testing and implementation, including serving as an Accessibility Testing Specialist at IBM, where she contributed to ensuring digital products met global accessibility standards.
In this conversation, Anitta breaks down the key ideas behind the WCAG 3.0 draft, including its new scoring model, expanded coverage for different user needs, and what organizations should start thinking about today, even though the final version of the standard is still a few years away.
Expert perspective: understanding WCAG 3.0
Anitta, we’ve been hearing a lot about the draft of WCAG 3.0. To start us off, what is the timeline for this, and should we be worried about our current compliance?
That’s the first thing everyone asks! W3C calls this the “exploratory” stage of WCAG 3.0 outcomes. The final version isn’t expected anytime before 2028, at least. So, no, there’s no need to panic today. However, it’s important to understand that WCAG 3.0 isn’t just a “version 2.3.” It’s a complete redesign of the framework. We are moving from a set of fixed success criteria to a model that offers more context, flexibility, and real-world accessibility value.
If it’s not just an “add-on” to WCAG 2.2, what makes it so fundamentally different?
While the core principles of accessibility stay the same, WCAG 3.0 introduces a new evaluation approach.WCAG 2.x is structured around testable success criteria that are often implemented as technical checklists. WCAG 3.0 is user-capability focused. It starts with the question: “What does the user need to be able to do?” rather than “What does the code need to look like?”
You mentioned “user-capability.” Does this mean WCAG 3.0 covers a wider range of disabilities than the current standards?
Absolutely. WCAG 3.0 still addresses the same broad accessibility needs as WCAG 2.x, but it places stronger emphasis on areas that were harder to measure before, especially cognitive accessibility. It also places a heavy emphasis on general usability. It’s about making sure a digital experience isn’t just “accessible” on paper, but actually usable and intuitive for everyone.
Let’s talk about the structure. WCAG 2.x uses Principles and Success Criteria. How does 3.0 organize things?
It’s a three-layered approach now:
1. Guidelines: The high-level accessibility goals.
2. Requirements: The specific conditions that must be met. They are further divided into three parts – core requirements, supplemental requirements, and assertions.
3. Tests/Techniques: The “how-to” for implementation and verification.
Within those “Requirements,” you mentioned they are divided into three types. Can you explain the difference between Core and Supplemental requirements?
Think of Core Requirements as your mandatory foundation; you must meet these to achieve any level of conformance. Supplemental Requirements build on top of that; they are about enhancing the quality and making the experience even smoother for the user.
There is a third category called “Assertions.” This is a new term in accessibility standards. What does it mean?
This is a very progressive addition. Assertions are documented statements by an organization about its accessibility practices. They cover things that an automated tool or a simple technical test can’t catch, such as the quality of a live sign language interpretation or internal accessibility processes. It allows organizations to get credit for the human-centric work they do.
One of the most significant changes seems to be how we “pass” an audit. How does the scoring work in 3.0?
This is where it gets exciting. In WCAG 2.x, it’s binary: you either Pass or Fail. If one image is missing alt-text, technically, the conformance is not met. WCAG 3.0 introduces a progressive scoring model. Requirements receive individual scores, which are then aggregated. This acknowledges partial progress and rewards continuous improvement rather than demanding perfection or nothing.
We are all used to the A, AA, and AAA levels. Are those going away?
Yes, the new conformance levels will be Bronze, Silver, and Gold. They are not exactly mapping to A/AA/AAA, but these tiers work with WCAG 3’s scoring model to measure overall accessibility performance.
Bronze is the new baseline, roughly comparable to AA.
Silver represents a higher level of usability support.
Gold is the “gold standard,” representing the pinnacle of inclusive design maturity.
Currently, we audit page by page. Does WCAG 3.0 change the “scope” of what we test?
It does. 3.0 is much more flexible. You can still test a single page, but you can also evaluate a specific user journey (like the process of buying a product), an entire product, or a whole website. This reflects how people actually use the internet, they don’t just look at one page; they move through a flow.
Does this version also look beyond just standard web browsers?
Yes. WCAG 2.x primarily focuses on web content. Where 3.0 expands support across mobile applications, emerging technologies, and even immersive/interactive environments like AR or VR. In short, 3.0 will be more adaptable to emerging technologies.
To give us a practical example, how would something like “Transcripts” be graded under this new system?
Under the 3.0 model, having the transcript would be a Core Requirement with a specific test. Ensuring the speakers are identified in that transcript would be a Supplemental Requirement. And if you provide live sign language, that would be an Assertion. Your total score across all three would determine if that media content hits Bronze, Silver, or Gold.
Final question, Anitta. Given that the final version is still a few years away, what should we be doing right now?
The best thing we can do is shift our mindset. While organizations should continue working toward current standards like WCAG 2.x, it’s helpful to begin thinking in terms of user journeys and functional needs. By focusing on the real user experience, rather than just passing a binary technical check, we’ll be better prepared for the direction WCAG 3.0 is moving toward. Ultimately, it’s about complementing compliance-driven work with a stronger focus on empathy-driven design.
Wrapping up
Although the final version of WCAG 3.0 is still a few years away, it signals a clear shift toward a more user-centered and flexible approach to accessibility. While organizations should continue following WCAG 2.x standards, it’s also a good time to start thinking beyond checklist-based compliance and focus more on real user experiences and inclusive design.
As Anitta highlights, the goal remains the same: creating digital experiences that work for everyone. WCAG 3.0 simply moves us closer to measuring accessibility in a way that better reflects how people actually use the web.
Ipshita Biswas 
