WCAG 3.0 Guidelines: what’s changing & what website owners need to know
Author: Dan Clark 19th Oct 2026 7 minutes read
Overview
Website accessibility guidelines are being updated, with the World Wide Web Consortium (W3C) publishing a new working draft of WCAG 3.0 in September 2026.
The proposed changes go beyond introducing additional accessibility requirements. They also include a different approach to measuring accessibility, with the aim of providing a more detailed picture of how well websites and digital services meet people’s needs.
For organisations managing existing websites or planning a redevelopment, it’s good to understand what’s being proposed. However, WCAG 3.0 is still several years away from becoming a completed standard, and many details are still under discussion.
So, what’s changing, and what – if anything – should website owners be doing now?
What is WCAG 3.0?
The Web Content Accessibility Guidelines (WCAG) provide internationally recognised recommendations for making websites and digital content accessible to people with disabilities.
The W3C develops them, and they help designers, developers, and organisations understand how to make digital services easier for everyone to use.
WCAG 3.0 is the next major generation of these guidelines.
Unlike WCAG 2, which mainly focuses on web content, WCAG 3.0 is intended to cover a wider range of digital experiences, including websites, applications, publishing tools and emerging technologies.
It’s also aiming to address a wider range of accessibility needs, including those of people with cognitive and learning disabilities.
Although it builds on earlier versions, WCAG 3.0 introduces a different way to organise requirements and assess whether they’re met.
What’s changed in the September 2026 update?
On 10 September 2026, the W3C published an updated WCAG 3.0 Working Draft alongside a revised document explaining how the proposed guidelines will work.
One of the most significant developments concerns the conformance model, which determines how accessibility is assessed and reported.
Under WCAG 2.2, organisations generally work towards one of three conformance levels, varying in strictness: A, AA or AAA.
The September draft proposes a different approach, using a single conformance level alongside reporting tiers that recognise progress towards meeting the requirements and improvements beyond them.
The intention is to provide a more informative way of reporting accessibility than simply identifying whether a particular level has been achieved.
However, the W3C is still seeking feedback on this approach, so the final model may well be different.
A different way of assessing accessibility
The proposed WCAG 3.0 model groups accessibility requirements according to the potential consequences of not meeting them.
These are currently divided into four categories.
Physical harm
Requirements where an accessibility failure could cause immediate physical harm to someone with a disability.
Risk
Requirements where a failure could unnecessarily increase financial, medical, legal, privacy or security risks.
Barrier
Requirements where a failure could prevent someone from completing an activity or progressing through a digital service.
Friction
Requirements where a failure could make an activity more difficult, even if it doesn’t prevent someone from completing it.
The proposed reporting system uses these categories to distinguish different levels of progress.
For example, the draft’s third reporting tier represents full conformance with all core requirements. Higher tiers would recognise additional accessibility measures and evidence of organisational practices.
This could give organisations a more detailed way to communicate accessibility improvements, particularly where substantial work has been completed but further issues remain.
It’s important to note that these categories and reporting arrangements are proposals. So they shouldn’t yet be used as an alternative to established WCAG 2.2 conformance assessments.
Why is WCAG 3.0 being developed to replace WCAG 2.2?
Websites and digital services have changed considerably since the earlier WCAG standards were introduced.
As with many established standards, keeping pace with new technologies and the ways people use them can be difficult. Requirements that worked well when first introduced may not fully address the accessibility challenges people face today.
People now interact with digital content through a wider range of devices, interfaces and technologies. Websites also contain increasingly complex functionality, from interactive applications to personalised services.
WCAG 3.0 aims to provide guidance that accommodates these developments while addressing accessibility needs that existing requirements haven’t always covered adequately.
The W3C also wants the guidelines to be easier to understand and more flexible across different technologies.
Another important consideration is how accessibility is measured.
Meeting individual technical requirements is essential, but accessibility also depends on whether people can successfully use a website or digital service.
The proposed changes aim to support a more detailed assessment of accessibility outcomes while retaining clear requirements that organisations can test.
Will WCAG 3.0 replace WCAG 2.2?
WCAG 3.0 is intended to become a new W3C accessibility standard, but that doesn’t mean WCAG 2.2 will immediately disappear.
The W3C has confirmed that WCAG 3.0 is still several years away from completion. It also expects WCAG 2 to remain in use for several years after the new standard is finalised.
For UK organisations, it’s particularly important to distinguish between the publication of accessibility guidelines and the legal requirements that apply to their websites.
Introducing a new W3C standard doesn’t automatically change those legal obligations. For now, WCAG 2.2 AA remains an appropriate benchmark for organisations looking to improve website accessibility.
What should website owners do now?
There’s no need to delay accessibility improvements or begin redesigning websites specifically around the proposed WCAG 3.0 requirements. In fact, you can’t, since nothing is finalised yet.
The most useful approach is to keep addressing accessibility through established standards while watching for future developments, or working with someone who’s doing that for you. This can include:
Review your existing website
An accessibility audit can identify problems affecting navigation, content, forms and interactive functionality.
Automated testing helps, but it won’t catch every accessibility issue. Manual checks, including keyboard navigation and assistive technology testing, are also important.
Work towards WCAG 2.2 AA
Working towards WCAG 2.2 AA is a sensible way to improve accessibility now, while also establishing a strong foundation for future standards such as WCAG 3.0.
Include accessibility in website planning
Consider accessibility when you’re thinking about requirements, designing interfaces, developing functionality, and preparing content.
Addressing problems early is almost always easier than fixing them after a website launches.
Consider ongoing accessibility responsibilities
Accessibility isn’t something you can action once and then forget about. Mistakes creep in.
New content, functionality and design changes can introduce problems, so regular testing and appropriate editorial guidance remain important.
What does this mean for organisations planning a website redesign?
If you’re planning a new website, the development of WCAG 3.0 is another reminder that accessibility needs to be part of the project from the beginning.
That doesn’t mean trying to implement requirements that are still being developed.
Instead, organisations should concentrate on building accessible websites that meet current standards and can be maintained as requirements change.
This includes choosing a content management system that supports accessible content, designing reusable components with accessibility in mind and establishing testing procedures throughout development.
Content editors will play a key role in keeping a website accessible after launch too. With this in mind, and while they need to understand the basics, the CMS should make it easier to manage content without needing specialist technical knowledge.
Too much flexibility can actually make accessibility harder to maintain. Website builders that offer endless layout options, colour pickers and styling controls can make it easy to introduce problems, even when the original website was built to meet accessibility standards.
Providing editors with accessible, pre-designed components and sensible controls helps reduce these risks while still giving them the flexibility to manage their content.
Looking ahead
WCAG 3.0 represents an important development in how website accessibility could be assessed and reported.
The September 2026 draft provides more detail on the proposed approach, but considerable work remains before it becomes a completed standard.
For website owners, the immediate priority is still the same.
Building accessible digital services, testing them properly and maintaining accessibility over time will remain important regardless of how future standards develop.
At Feel Created, we use WCAG 2.2 AA as our accessibility baseline when designing and developing websites. We also recognise that accessibility needs ongoing attention, particularly as content and functionality change.
We’ll continue to follow the development of WCAG 3.0 and what it means for organisations managing websites and digital platforms.
