WCAG 3.0 is the next generation of accessibility guidance from the W3C, but it is still a Working Draft and not a finalized standard. While WCAG 3 introduces a broader framework for evaluating websites, apps, and digital experiences, WCAG 2.2 remains the current benchmark organizations should follow while monitoring future WCAG developments.
WCAG 3.0 Explained: What Businesses Should Know
Key Takeaways
- WCAG 3.0 is the next generation of accessibility guidance from W3C, but it is still a Working Draft and not yet a finalized standard.
- WCAG 2.2 remains the current accessibility benchmark used by most policies, regulations, and procurement requirements.
- WCAG 3 introduces a broader framework that evaluates websites, apps, tools, and full user journeys, not just individual pages.
- The draft framework explores a new conformance model with Bronze, Silver, and Gold levels instead of A, AA, and AAA.
- Businesses should continue improving accessibility against WCAG 2.x standards today while monitoring WCAG 3 developments.
Introduction
WCAG 3.0 is receiving increasing attention in accessibility, design, and product teams. Many organizations are asking the same questions:
- Is WCAG 3.0 already released?
- How is WCAG 3.0 different from WCAG 2.2?
- What should businesses do today to prepare?
The key point is simple: WCAG 3.0 is still under development.
WCAG 2.2 remains the current W3C Recommendation and the accessibility benchmark referenced by most policies, regulations, and procurement requirements today.
WCAG 3 should therefore be viewed as the future direction of accessibility guidance, not an immediate replacement for existing standards.
If you are looking for a quick definition of the upcoming accessibility standard, see our WCAG 3.0 glossary page.
WCAG 2.2 vs WCAG 3.0: Key differences
The biggest changes between WCAG 2.2 and the WCAG 3 draft relate to scope, structure, and how accessibility is evaluated.
Topic | WCAG 2.2 | WCAG 3.0 draft | What it means for businesses |
|---|---|---|---|
Status | Current W3C Recommendation | Working Draft | WCAG 2.2 remains the current benchmark |
Scope | Primarily web content | Websites, apps, tools, publishing, emerging tech | Accessibility reviews may extend beyond websites |
Structure | Principles, guidelines, success criteria | Guidelines, requirements, methods, assertions | Accessibility becomes more process-focused |
Conformance model | A, AA, AAA | Bronze, Silver, Gold (under exploration) | Future evaluation may be more flexible |
Evaluation style | Mostly pass/fail | Mix of measurable and qualitative testing | Human testing may become more important |
Focus | Page-level evaluation | Views, task flows, and products | Testing may focus on full user journeys |
Cognitive needs | Covered but limited | Expanded focus | Content clarity and usability may gain more attention |
In simple terms:
WCAG 2.2 defines today's accessibility expectations.
WCAG 3 shows where accessibility guidance may evolve next.
What is WCAG 3.0?
WCAG 3.0 is the draft successor to WCAG 2.2 developed by the W3C Web Accessibility Initiative (WAI).
One visible change is the name itself.
- WCAG 2 = Web Content Accessibility Guidelines
- WCAG 3 = W3C Accessibility Guidelines
The updated name reflects a broader scope. Instead of focusing mainly on web pages, WCAG 3 is designed to apply to:
- websites
- web applications
- digital tools
- publishing systems
- emerging web technologies
The framework is being designed to better reflect how modern digital products work, including complex interfaces, dynamic applications, and multi-step user journeys.
However, WCAG 3 remains incomplete and evolving. W3C notes that many parts of the framework are still exploratory and may change significantly before final publication.
Why WCAG 3.0 is being developed
WCAG 2 has been highly influential for more than a decade. But it was originally created in a digital environment dominated by traditional websites.
Modern digital services are more complex. Many organizations now operate:
- web applications
- account portals
- product dashboards
- multi-step onboarding flows
- mobile-style web experiences
The goals of WCAG 3 include:
- making accessibility guidance easier to understand
- addressing a broader range of disability needs
- expanding support for cognitive accessibility
- adapting accessibility evaluation to modern digital products
Another goal is to move beyond page-based testing toward evaluating how users complete real tasks across a digital experience.
The biggest changes businesses should know
Several changes in the WCAG 3 draft may affect how organizations approach accessibility in the future.
Broader scope
WCAG 3 is intended to apply to more than traditional web pages.
W3C says the framework should support accessibility across:
- websites
- apps
- digital tools
- publishing systems
- emerging technologies
For businesses, this means accessibility planning may need to cover entire digital products, not only website pages.
A different conformance model
WCAG 2 uses the familiar A, AA, and AAA conformance levels.
WCAG 3 is exploring a different model with Bronze, Silver, and Gold levels.
The idea is to encourage a more flexible evaluation of accessibility efforts rather than relying entirely on pass-or-fail testing.
More qualitative testing
Many WCAG 2 checks can be evaluated objectively.
However, accessibility also includes areas where human judgment matters, such as:
- whether alternative text is meaningful
- whether instructions are understandable
- whether navigation flows are intuitive
WCAG 3 introduces more room for qualitative evaluation alongside automated checks. These evaluations often involve accessibility testing methods such as keyboard testing and screen reader reviews.
Focus on task flows and user journeys
WCAG 2 evaluation often focuses on individual pages.
WCAG 3 moves toward evaluating entire user journeys, such as:
- signing up for an account
- completing a purchase
- submitting a form
- recovering account access
- downloading documents
This reflects how real users experience digital products.
More attention to accessibility processes
WCAG 3 introduces the concept of assertions.
Assertions describe documented practices that support accessibility, such as:
- accessibility training
- testing procedures
- review workflows
- ongoing improvement processes
This suggests accessibility maturity may involve organizational practices, not only code fixes.
Practical examples
The difference between WCAG 2.2 and WCAG 3 becomes clearer when applied to real business scenarios.
E-commerce checkout
WCAG 2.2 approach
Evaluate each page for issues like:
- form labels
- keyboard navigation
- contrast
- error messages
WCAG 3 perspective
Look at whether the entire purchase journey works smoothly from cart to confirmation.
Customer portal login
WCAG 2.2 approach
Review individual screens.
WCAG 3 perspective
Evaluate whether users can successfully:
- log in
- recover access
- understand account information
- complete account tasks
Downloadable documents
WCAG 2.2 approach
Evaluate the PDF itself.
WCAG 3 perspective
Consider the broader experience:
- Can users find the document?
- Can they open it easily?
- Can they understand the content?
How businesses should prepare today
Even though WCAG 3 is still developing, businesses can take practical steps now.
Continue improving against WCAG 2.2
WCAG 2.2 remains the current accessibility benchmark used in most policies and regulations.
Organizations should continue improving digital accessibility based on current WCAG standards.
Test full user journeys
Accessibility barriers often appear across multi-step interactions.
Organizations can review important flows such as:
- account registration
- login and authentication
- checkout processes
- document downloads
- support requests
Testing these journeys often reveals issues missed during traditional accessibility audits.
Combine automated and manual testing
Automated scanning tools remain valuable, but they cannot detect every issue.
Many accessibility problems require:
- keyboard testing
- screen reader testing
- content clarity review
- usability evaluation
Combining automated and manual testing provides a more complete accessibility review.
Build accessibility processes
WCAG 3 highlights the importance of structured accessibility practices.
Organizations may benefit from documenting:
- testing procedures
- review workflows
- accessibility training
- remediation processes
Clear internal processes support more consistent accessibility improvements.
WCAG 3.0 timeline and status
One of the most common questions about WCAG 3 is its release timeline.
Item | Status | What businesses should know |
|---|---|---|
WCAG 2.2 | Final W3C Recommendation | Current accessibility benchmark |
WCAG 3.0 | Working Draft | Still evolving |
Release timeline | No fixed date | Final publication may take several years |
Legal adoption | Limited today | Most policies reference WCAG 2.x |
Recommended focus | Improve current accessibility | Monitor WCAG 3 developments |
Because WCAG 3 is still developing, businesses should treat it as a roadmap rather than a replacement for current standards.
What WCAG 3 means for accessibility
WCAG 3 represents a shift in how accessibility guidance may evolve.
The direction emphasizes:
- broader digital product coverage
- stronger attention to user experience
- more focus on cognitive accessibility
- evaluation across full user journeys
- structured accessibility practices
At the same time, WCAG 2.2 remains the current foundation for accessibility work.
Organizations should continue improving accessibility today while staying informed about future developments.
Key takeaway
WCAG 3.0 is the draft future of accessibility guidance, not the present-day replacement for WCAG 2.2.
For businesses, the most practical approach today is to continue improving digital experiences using current accessibility standards while preparing for the broader direction WCAG 3 signals.
Frequently asked questions
WCAG 3.0 is the draft successor to WCAG 2.2 developed by the W3C. It expands accessibility guidance beyond web pages to include apps, tools, and broader digital experiences.
No. WCAG 3.0 is still a Working Draft and may change significantly before it becomes a final standard.
WCAG 2.2 uses a structured set of success criteria with A, AA, and AAA conformance levels. WCAG 3 introduces a broader framework with a different structure, expanded scope, and potential Bronze, Silver, and Gold conformance levels.
No. W3C has stated that WCAG 2 will remain active for several years even after WCAG 3 is finalized.
WCAG itself is not a law. However, many accessibility regulations and policies reference WCAG as the technical standard used to evaluate digital accessibility.
Adam is the Head of Digital Marketing at Clym, where he leverages his diverse expertise in marketing to support businesses with their compliance needs and drive awareness about data privacy and web accessibility. As one of the company’s original team members, Adam has been instrumental in shaping its journey from the very beginning. When he’s not diving into marketing strategies, Adam can be found cheering on his favorite sports teams or enjoying fishing.
Find out more about Adam