WCAG 3.0 overview and update 2026
As outlined in the following post, WCAG 3.0 is still heavily in development. The information below is based on the current version at time of update - February 2026.
Background to the upcoming Version 3.0 of the Web Content Accessibility Guidelines (WCAG).
Key questions answered in this document are:
- What is WCAG 3.0?
- Why are there new WCAG 3.0 standards being developed?
- How does WCAG 3.0 fit in with other accessibility standards?
- When is WCAG 3.0 expected to be finalised?
- What is the release date of WCAG 3.0?
- What are the key updates in WCAG 3.0 compared to previous versions?
- How will WCAG 3.0 impact web development practices?
- Does WCAG 3.0 mention AI and accessibility?
- How do I prepare my website for WCAG 3.0?
- Which accessibility testing tools support WCAG 3.0 guidelines?
- How will accessibility be measured in WCAG 3.0?
- Where can I read the latest draft of the WCAG 3.0?
What is WCAG 3.0?
WCAG 3.0 is the next generation of digital accessibility standards from the W3C (World Wide Web Consortium).
In earlier guidelines (WCAG 1.0 through to WCAG 2.2), the WCAG acronym stands for Web Content Accessibility Guidelines. In WCAG 3.0, WCAG stands for W3C Accessibility Guidelines.
This name change emphasises the move towards guidelines that cover more than web content. This is in line with the recent (Oct 2025) W3C rebranding, which introduced the new logo (shown here) and tag line “making the web work — for everyone”.
Why are there new WCAG 3.0 standards being developed?
To cover more than just web content
To extend the standards beyond just web pages and web content. Whilst WCAG 2.2 applies primarily to web pages, WCAG 3.0 aims to support:
- Augmented / virtual reality
- Digital content e.g. Office documents and presentations, PDFs
- Authoring tools e.g. Content Management Systems (CMSs) such as WordPress, Adobe Experience Manager
- User agents e.g. browsers and assistive technologies
- Software including mobile apps
- Web applications e.g. Google Docs, Office 365
- Operating systems
For easier maintenance
The current standards have a lengthy revision process, which makes developing and releasing updates challenging. WCAG 3.0 is intended to be more regularly updated, to better reflect the evolving technological landscape of the web.
To be more inclusive
WCAG 3.0 also aims to support more disabilities and impairments. For example, WCAG 2.2 has typically focused more on sensory and physical impairments, but cognitive impairments – affecting comprehension, language and so on – have not been covered as much. WCAG 3.0 aims to remedy this and be more broadly inclusive.
For example, some of the in-development requirements for WCAG 3.0 include:
- Explanations or unambiguous alternatives are available for non-literal language, such as idioms and metaphors.
Figurative language, such as the English idiom “Don’t count your chickens before they hatch” can be difficult to understand for people who have English as a second language, or for autistic people.
Another guideline demonstrates how VR/XR can be supported by requiring that captions, in 360 environments such as VR experience, are appropriately positioned for readability:
- In 360-degree digital environments, captions remain directly in front of the user.
How does WCAG 3.0 fit in with other accessibility standards?
There are currently multiple accessibility standards available for different purposes, for example:
- Authoring Tool Accessibility Guidelines (ATAG)
- User Agent Accessibility Guidelines (UAAG)
- Mobile Web Best Practises (MWBP)
- Web Content Accessibility Guidelines (WCAG)
WCAG 3.0 harmonises current disparate standards into a single resource, which will be both easier to refer to and to maintain.
Note that WCAG 2.2 will not be deprecated when WCAG 3.0 is published. WCAG 2.2 remains in use around the world, embedded into legislation (e.g. Public Sector Bodies Accessibility Regulations, or PSBAR, in the UK), and is likely to remain in use for some time. Having both standards live at once allows for a more gradual transition to WCAG 3.0.
When is WCAG 3.0 expected to be finalised?
WCAG 3.0 is currently in development and has been since 2016. Whilst it was speculated early on that WCAG 3.0 could have been launched in 2023, the current timeline suggests the guidelines won’t be finalised before 2028.
The nature of the W3C standards process is that new standards, such as WCAG 3.0, move through multiple stages (The W3C Recommendation Track) before publication.
WCAG 3.0 is currently published as a Working Draft, which reflects that there is still a lot of work being done. This is an iterative process, and there will be more revisions to this working draft as work continues.
The 4 stages the guidelines progress through are:
- First working draft (Published in Jan 2021)
- Revised working draft (first published in June 2021, and most recently in September 2025). This is the current stage. It is likely that there will be multiple more revisions before progressing to stage 3.
- Candidate recommendation. Anticipated in Q4 of 2027.
- W3C recommendation. This is a W3C endorsed specification, and ready for use. By the current timelines, this will not be earlier than 2028.
What is the release date of WCAG 3.0?
The WCAG 3.0 timeline suggests that a draft candidate recommendation is planned for Q4 2027. Whilst this is the final stage before progressing to a recommendation, there may well be significant amends to the standards at this point.
What are the key updates in WCAG 3.0 compared to previous versions?
Scope
WCAG 3.0 allows for scoping of views or processes or a combination of the two.
A view is defined as content that is actively available – e.g. can be read and interacted with – in the viewport. By this definition, a modal dialog would be considered a discrete view. The nature of modal dialogs is that they are presented in isolation - the background view from which they were invoked is not available whilst the modal is displayed.
A process is a series of views, often completed in a certain order. These may span multiple sites.
This moves the focus away from the concept of pages used in WCAG 2.2 which are explicitly associated with URIs. (A URI is a Uniform Resource Identifier, or a specific web address.)
Conformance
WCAG 2.2 conformance was evaluated through binary success criteria (SC); each success criteria could be passed, meaning the page contained content that conformed to the SC OR did not include any content that failed the SC, OR the SC could be failed if the content did not conform.
In addition, conformance to WCAG 2.2 was also very binary – a page could conform or not conform.
WCAG 3.0 uses a different conformance model, with different sets of requirements:
- Foundational requirements
- Supplemental requirements
- Assertions
These can allow for differing levels of conformance. For example, satisfying all of the foundational requirements is intended to be broadly equivalent to the existing WCAG 2.2 AA standard.
Organisations could go further by satisfying the supplemental requirements to demonstrate greater conformance. This could lead to conformance levels such as gold, silver, bronze, or similar, being available for use.
Assertions relate to the processes involved in creating and publishing content or products. These could allow for organisations to demonstrate commitment to accessibility at a cultural or process level.
This is similar to the European Accessibility Act (EAA), which has a much more holistic view of accessibility, and emphasises the importance and need for organisations to embed accessibility throughout as opposed to measuring compliance purely on technical audits.
Plain language
A frequent concern with WCAG 2.0 is the inaccessibility of the documentation; it is often technical and can be challenging to read – even for people familiar with them.
WCAG 3.0 has introduced plain language summaries for key sections of the specification to address this concern and make content easier to read.
How will WCAG 3.0 impact web development practices?
The current conformance model for WCAG 3.0 moves beyond the strict standards compliance approach of WCAG 3.0. Whilst there will still be technical requirements to meet, there is an opportunity for organisations to go beyond standards compliance, and make assertions about their broader approach to web development. The WCAG 3.0 explainer document gives some example assertions, including:
- Accessibility training (for staff) has been provided
- Testing with assistive technology (as opposed to purely code level compliance)
- Documentation of accessiblity processses (e.g. testing approaches, how issues are managed, prioritised and triaged)
Including assertions in a conformance claim could allow for a higher level of conformance to be claimed.
This echoes some of the principles of the European Accessibility Act, which emphasises the need to go beyond compliance, and embed accessibility into organisational culture.
Does WCAG 3.0 mention AI and accessibility?
WCAG 3.0 explicitly mentions the use of AI (artificial intelligence) with regards to content. The following two statements are assertions - formal claims, or statements of fact, that content authors can make. As above, making these declarations could allow for a higher level of conformance to be claimed.
"If AI tools are used to generate or alter content, the content author(s) have a documented process for a human to review and attest that the content is clear and conveys the intended meaning."
and:
"Content author(s) train AI models using representative and unbiased disability-related information that is proportional to the general population."
This recognises that AI will likely play a role in creating content but aims to counteract some of the harmful aspects - such as inherent bias in large language models currently in use. This approach recognises that a more responsible approach to using AI, with appropriate human governance, can lead to better user experiences.
How do I prepare my website for WCAG 3.0?
At present, organisations should continue to treat WCAG 2.2 as the de facto standard for web accessibility. A website that is WCAG 2.2 AA conformant is likely to be broadly conformant to WCAG 3.0's core requirements.
WCAG 3.0 is still in development, and is likely due for release no earlier than 2028. There is opportunity for significant change in the intervening, so attempting to meet the guidelines in their current state is no guarantee of conformance with the final specification.
That said, WCAG 2.2 (and likely WCAG 3.0) should be treated as the starting point for accessibility and not the end goal.
For example, adopt an inclusive design approach and seek out views and feedback from people with diverse abilities. This can help you go beyond conformance, and make products more usable. This will of benefit now, and is unlikely to be at odds with any WCAG 3.0 developments.
Which accessibility testing tools support WCAG 3.0 guidelines?
At the moment, no testing tools can be guaranteed to support WCAG 3.0 as the guidelines are still heavily in development, and therefore subject to change.
It is likely that many of the current automated tools will be updated to support WCAG 3.0 in the future though as there will be a lot of common requirements between WCAG 2.2.
For example, the need for content to be well structured with headings, make good use of lists, and so on. It is likely that tools for testing this aspect of WCAG 2.2 will be adapted to do the same with WCAG 3.0.
How will accessibility be measured in WCAG 3.0?
WCAG 2.2 is very binary. Pages are tested against individual success criterion (SC), and then each of these success criteria is passed or failed accordingly. A website can only be WCAG 2.2 conformant if all of the pages have no failures (or there is accessible alternatives provided). There is no partial conformance.
WCAG 3.0 may include a more flexible system where content or functionality can be evaluated at several levels, allowing for differing levels of conformance. This part of WCAG 3.0 is still being progressed, so it is not yet clear how this will look in practise.