‍WCAG 2.2 level AA: A Comparison to 2.1

In this blog I will discuss the changes that have occurred from Web Content Accessibility Guidelines (WCAG) 2.1 level AA to WCAG 2.2 level AA.

What are the Web Content Accessibility Guidelines?

The Web Content Accessibility Guidelines (WCAG) are a set of international standards designed to improve web content accessibility for individuals with impairments. WCAG provides a variety of proposals for making web material simpler to perceive, interpret, browse and engage with. They aim to provide a single and common standard that serves the demands of all.

The Different WCAG Versions:

WCAG 2.1: Released in June 2018, expanded on (WCAG 2.0) by introducing addition to address concerns with, limited eyesight, and. It attempted to fill the gaps that have emerged after the publication of WCAG 2.0 in 2008.

WCAG 2.2: The most recent version, issued in December 2020, builds on WCAG 2.1 by incorporating new success criteria to improve online accessibility. WCAG 2.2 contains new rules to increase, give alternatives for dragging movements, make it simpler to get support and streamline authentication processes.

New Additions

There are four major additions to WCAG 2.2, there are as follows:

1. Focus Appearance (2.4.11): This means including minimal focus appearance criteria to ensure that focus indications are displayed. This is especially crucial for people who navigate using keyboards.

2. Dragging Movements (2.5.7): This criterion mandates that every feature that involves dragging movements provide an alternate technique that benefits users with motor limitations.

3. Findable Help (3.2.6): Allows users to easily discover help choices. This might contain a help link, chat assistance, or a FAQ section to aid people who are having difficulty locating support on their own.

4. Accessible Authentication (3.3.7): This criteria is critical for ensuring that users with cognitive impairments may authenticate without encountering significant impediments. It encourages alternate cognitive function assessments, such as CAPTCHA.

Other Changes

One significant change in WCAG 2.2 is the removal of Success Criterion 4.1.1 (Parsing). Previously, this rule required that HTML and XML code be properly structured to avoid issues like incorrectly closed tags and duplicate attributes. However, WCAG 2.2 now considers this rule outdated because modern parsers can usually handle these small errors without causing major problems. A note added to WCAG 2.1 and 2.0 even states that this rule should always be considered met for HTML or XML content. Despite this change, developers should still follow good coding practices to ensure overall code quality.

It's also crucial for automated testing tools to be updated to reflect WCAG 2.2 standards. Outdated tools might still flag parsing errors and provide incorrect advice. By removing this criterion, WCAG 2.2 allows developers to focus on more important issues, ultimately creating a better web experience for everyone.

Understanding the updates from WCAG 2.1 to WCAG 2.2 is crucial for ensuring your website remains accessible to all users. The new criteria introduced in WCAG 2.2 aims to address emerging accessibility needs and simplify the user experience for individuals with various. By adhering to these guidelines, you can create a more inclusive digital environment.

‍

At Cali Digital, we specialise in inclusive design and are committed to helping you integrate accessibility seamlessly into your next project. Cali Digital can assess your digital app/website against these new accessibility criteria. Contact us to book a time to discuss your requirements.

‍

References

Web Accessibility Initiative (2018). WCAG 2.1 at a Glance. Web Accessibility Initiative (WAI)

Initiative (WAI), W.W.A. (2023). What’s New in WCAG 2.2 Draft. Web Accessibility Initiative (WAI).

‍

‍