WCAG 3.0 - What the new Working Draft means for accessibility

Last month, the W3C released an updated “Working Draft” of WCAG 3.0. A Working Draft means that the standard is still under active development, with many sections in “Developing” or “Exploratory” mode. Iterating on several “Working Drafts” and inviting public feedback is the first step in creating a new standard. 

‍

Key changes introduced in WCAG 3.0

Our designers and developers are very familiar with WCAG 2.2 and have eagerly taken a look at the new draft. Here are some of the big changes we could be getting!

• A new scoring model with severity & weighted grading - One of the most promising features of WCAG 3.0 is the introduction of a scoring model that uses severity levels and weighted grading. This is a game-changer! Instead of viewing accessibility as a simple pass/fail checklist (which is rarely the case when examining accessibility scenarios closely or dealing with legacy code), the new approach prioritises issues with the most tangible effect on users. By providing a more balanced and realistic assessment of accessibility, the model not only captures people’s real experiences but also helps designers and developers make gradual, meaningful improvements over time.
  
  
• Involving people with diverse disabilities in testing - this marks a positive shift from compliance-focused development to genuinely human-centred accessibility. Although usability can be subjective and assessors and creators may interpret outcomes differently, the move to incentivise real-world accessibility outcomes is a step in the right direction.
  
  
• Not just for developers - WCAG variations have also traditionally been very technical, tricky to navigate and hard for designers and content writers to engage with. WCAG 3.0 is looking to implement a new structure that includes guidelines (accessibility goals), outcomes (testable user statements) and methods (techniques for achieving accessible outcomes). This approach makes accessibility guidance easier to understand and apply across different disciplines, not just in code. It helps ensure that accessibility can be designed in from the start, rather than being retrofitted later.

‍

When to expect WCAG 3.0 and what to do in the meantime

There isn’t a detailed timeline for WCAG 3.0, although W3C expects it will take a few years before it becomes an official recommendation. It’s a huge undertaking as this is being developed as a completely new standard, and once it is final, it won’t automatically supersede WCAG 2.2. A direct replacement wouldn’t be practical for many reasons, one being that the two standards side by side simply won’t align. We expect that software teams and organisations will go through a transition period during which both standards are in use. This underscores the importance of staying informed about the development of WCAG 3.0. There may be ideas you can adopt before the standard is finalised, such as testing early with a broad range of people with different abilities and access needs so that you can get feedback on real user experiences. 

We’ve only scratched the surface in highlighting some of the cornerstone changes being explored in WCAG 3.0. It’s an exciting time to see a complete overhaul (WCAG 2.0 was released in 2008!) and a thorough rethink of how we approach accessibility. There’s plenty to like about the direction the new standard is taking.

‍

Stay in the loop

If you want to stay up to date with the W3C’s efforts, you can subscribe to WAI news directly.

If you need help building accessible and inclusive software, chat with us here at Airteam. We love building things better!