Expanding Beyond Web Content

WCAG 3.0 is designed to go far beyond traditional web pages. While WCAG 2.2 primarily focuses on web content, WCAG 3.0 aims to support a much wider range of digital experiences, including augmented and virtual reality, mobile apps, operating systems, web applications such as Google Docs and Office 365, digital documents like PDFs and presentations, authoring tools such as content management systems, and user agents including browsers and assistive technologies.

This broader scope reflects how people now interact with digital content across many different platforms and environments.

Easier to Maintain and Update

One of the challenges with earlier versions of WCAG has been the lengthy revision process, which makes updates slow and complex. WCAG 3.0 is intended to be more flexible and easier to update, allowing it to respond more effectively to changes in technology and the evolving digital landscape.

A More Inclusive Approach

WCAG 3.0 also aims to support a wider range of disabilities. Earlier guidelines have often focused more heavily on sensory and physical impairments, with less emphasis on cognitive impairments that affect comprehension and language. The new version seeks to address this gap.

For example, draft requirements include providing clear explanations for idioms and figurative language that may be difficult for people with cognitive disabilities, autistic users, or those who speak English as a second language. Other proposed guidance includes ensuring captions in 360-degree virtual environments remain positioned directly in front of the user for readability.

Aligning Accessibility Standards

Currently, there are multiple accessibility standards serving different purposes, such as ATAG, UAAG, MWBP, and WCAG. WCAG 3.0 aims to bring these separate resources together into a more unified and streamlined framework, making them easier to reference and maintain. Importantly, WCAG 2.2 will not be withdrawn when WCAG 3.0 is introduced.

Since WCAG 2.2 is embedded in legislation in many countries, including the UK, both versions are expected to operate alongside each other for some time, allowing for a gradual and practical transition.

Preparing Your Website for WCAG 3.0

  • Continue following WCAG 2.2 – Treat WCAG 2.2 AA as the current standard. A site conformant to WCAG 2.2 is likely to meet the core requirements of WCAG 3.0.

  • Use inclusive design practices – Engage with users of diverse abilities, gather feedback, and design accessibility into your workflows. This approach goes beyond mere conformance and will remain valuable under WCAG 3.0.

  • Testing tools – No tools currently fully support WCAG 3.0, as it is still in development. Many existing WCAG 2.2 tools are likely to be updated once WCAG 3.0 is finalised.

  • Conformance measurement – WCAG 3.0 aims to provide a more flexible system than the binary pass/fail model of WCAG 2.2. This may allow for varying levels of conformance, but details are still being finalised.

In short, focus on accessibility now using WCAG 2.2 and inclusive design principles, while staying prepared to adapt to the final WCAG 3.0 guidelines when they are released.

WCAG 3.0 has been in development since 2016 and is still evolving, with finalisation not expected before 2028. It is currently at the Revised Working Draft stage, with further updates planned, followed by a Candidate Recommendation in late 2027. While the final guidelines may still change, now is a great time to get ahead and prepare your website for the next generation of accessibility standards.

Contact us to see how we can help you stay ready and ensure your site is inclusive and future-proof.