What Can You Expect from WCAG 3.0

What is the Status of WCAG 3?

WCAG 3.0 is still in an exploratory phase but is expected to change substantially before WCAG 3 is finalised. The W3C (the World Wide Web Consortium), which publishes the guidelines, released a working draft on 12 December 2024, but there is no date yet for a final version; the W3C has implied that it may still be a few years off (source). Nevertheless, although it may be some time before the new guidelines come into effect, there is already a lot of information available about their scope and changes, giving you plenty of time to prepare for their implementation.

Who is Developing WCAG 3?

The WCAG technical documents are developed by the Accessibility Guidelines Working Group (AG WG) with the Silver Community Group. These Groups are part of the World Wide Web Consortium (W3C) Web Accessibility Initiative (WAI).

Can you be involved in WCAG 3.0?

W3C collaborates with many stakeholders to compile the guidelines and welcome ideas and contributions. They are, currently, particularly looking for feedback on the following:

• Image alternatives guidelines
• Keyboard focus appearance guidelines
• Clear meaning guideline
• Conformance

Learn more about how you can contribute to WCAG 3.0.

 

What is the Scope of WCAG 3?

As with previous versions, with WCAG 3, W3C aim to explain how to make the web more accessible to people with disabilities. It will cover web content, apps, tools, publishing, and emerging digital technologies. However, instead of adding to the existing guidelines, WCAG 3.0 will rethink the structure and testing approach to address known problems with current versions, such as technical language and reductive grades. An increased emphasis on the practical application of accessibility principles will give designers and developers clearer guidance on achieving each success criterion. Furthermore, the new guidelines are intended to cover more user needs, including those of people with cognitive disabilities and be flexible to address different types of web content, apps, tools, and organisations.

What’s Changing with WCAG 3?

The Guidelines’ Name

The guidelines’ name is changing from WCAG 2—Web Content Accessibility Guidelines to WCAG 3 – W3C Accessibility Guidelines. But, don’t worry, If you still refer to it as WCAG 3, everyone will know what you mean, WSC said “W3C Accessibility Guidelines (WCAG) 3.0” was chosen because of widespread familiarity with the “WCAG” acronym and to encompass the broader scope beyond “content” (source).

What will the Structure of WCAG 3 Be?

WCAG 3.0 will be comprised of Guidelines and Requirements.

Guidelines

Guidelines are high-level, simple-to-understand, user-centered outcome statements. They help a wider audience understand the difficulties that disabled people face online. They address specific issues on topics like contrast forms and readability. For example;

• Text alternatives
• Headings and Structure
• Colour contrast

Each guideline will include multiple requirements that are designed for use by developers, testers and other technical specialists.

Foundational Requirements

These will be used to test basic levels of accessibility requirements and are equivalent to AA requirements in the WCAG 2 guidelines. Foundational Requirements will include things like:

• Providing alternative text for images
• Ensuring all content has keyboard access
• Giving clear focus indication for interactive elements

Supplemental Requirements

Supplemental Requirements will be additional to the Foundational Requirements and be used to assess higher levels of requirements.

Testing and Conformance

The old levels of conformance, A, AA and AAA, are changing to Bronze, Silver and Gold. The new levels are designed to identify and prioritise critical errors so developers and designers can address them promptly and effectively. A Bronze accreditation will be similar to WCAG Level AA. Alongside the new levels, there will be new testing mechanisms and scoring in place to determine how a website performs and which level it will receive. The new approach is designed to provide more flexibility and practicality in evaluating accessibility. By employing a combination of pass/fail and graded scores, W3C aim to achieve nuanced assessments of a website’s accessibility.

Quantitative Testing

Quantitative tests will focus on individual components of a page such as buttons, forms, images and navigation menus. They break down accessibility criteria into smaller, more manageable parts, to get a detailed assessment of specific aspects of a website’s accessibility. Focusing on individual elements and interactions means quantitative tests can identify and address critical accessibility issues more effectively. Quantitative tests will usually result in a pass/fail outcome and will be used to assess Critical Errors. They are required to achieve a bronze rating.

Qualitative Testing

Qualitative testing is being introduced to WCAG 3 to simulate more ‘real-life testing’ as, even if a site passes all atomic tests, it may not be accessible to all users across all assistive technologies. Qualitative testing may include testing with assistive technologies, usability testing and cognitive walkthroughs.

How Will WCAG 3 Be Scored?

The scoring system is still being developed, but the current approach uses dual testing to go beyond pass or fail and show progress towards a goal. To meet the Bronze level, a website will likely have to meet Foundational Requirements, and to move up to Silver or Gold it will need to score well on the Supplementary Requirements too. However, the exact breakdown of criteria is still being decided on.

When Will WCAG 3.0 be Enforced?

WCAG 3.0 is intended to succeed but not deprecate WCAG 2. W3C has said that organisations can choose to continue using 2 or migrate to 3. Nevertheless, JBi believes organisations demonstrate a stronger commitment to accessibility if they choose to use WCAG 3, as this is likely to have a more thorough testing process. It remains to be seen whether the legislation outlining the responsibilities of public bodies will be updated to reflect WCAG 3 or continue to be based on WCAG 2.