What's Changed in WCAG 2.2: Level A and AA Quick Reference Guide

The Web Content Accessibility Guidelines (WCAG), created by the World Wide Web Consortium (W3C) are the internationally accepted standard for incorporating accessibility into digital assets, including websites, applications, and other software. The newest version of the WCAG, version 2.2, became an official recommendation on October 5th, 2023.

Since the WCAG is a living document and gets updated periodically, WCAG 2.2 is slightly different than the older WCAG 2.1. Most of these differences come in the form of additional success criteria; however, there is also one success criterion that was removed.

Below, we'll list all Level A and Level AA changes in WCAG 2.2. While there are 3 additional Level AAA success criteria that have been added to WCAG 2.2, Level AAA is not currently (as of the publishing of this document) a requirement to meet most compliance standards in countries around the world. All information in this quick reference guide directly references the W3C’s WCAG 2.2 document, which you can view in detail at this link.

What's Been Removed

Only one success criterion was removed with the update from WCAG 2.1 to version 2.2 – 4.1.1: Parsing.

4.1.1: Parsing

Success Criteria 4.1.1 Parsing has been removed and has not been replaced by another one. This criterion dealt with following appropriate HTML standards and requirements.

The W3C specifically states, “With today’s technology, accessibility issues that would have failed 4.1.1 will fail other criteria, such as Info and Relationships (SC 1.3.1) or Name, Role, Value (SC 4.1.2). Therefore 4.1.1 is no longer needed for accessibility.”

What's Been Added

There are 6 new success criteria in the WCAG 2.2 that fall under Level A and Level AA requirements.

2.4.11: Focus Not Obscured (Level AA)

When a user interface component receives keyboard focus, the component is not entirely hidden due to the author-created content.

Example of a 2.4.11 Failure: “This page has a big banner that’s always across the bottom (a sticky footer). When I move focus to items, some are hidden behind the banner, and I can’t see them.”

2.5.7: Dragging Movements (Level AA)

All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging, unless dragging is essential or the functionality is determined by the user agent and not modified by the author.

Example of a 2.5.7 failure: “I cannot hold down the mouse button and drag it accurately enough to move the items in this list.”

2.5.8: Target Size (Level AA)

The size of the target for pointer inputs is at least 24 by 24 CSS pixels, with exceptions for Spacing, Equivalence, Inline, User Agent Control, and Essential.

Example of a 2.5.8 failure: “The buttons are so close, I hit ‘Cancel’ when going for ‘Submit.’ Then I have to start all over again.”

3.3.7: Redundant Entry (Level A)

Information previously entered by or provided to the user that is required to be entered again in the same process is either auto-populated or available for the user to select, except when:

• Re-entering the information is essential.

• The information is required to ensure the security of the content.

• Previously entered information is no longer valid.

Example of a 3.3.7 failure: “Whenever I use the online app to schedule my medical appointments, I have to retype some information that I entered in a previous step.”

3.3.8 Accessible Authentication (Level AA)

A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless that step provides at least one of the following:

• Alternative: Another authentication method that does not rely on a cognitive function test.

• Mechanism: A mechanism is available to assist the user in completing the cognitive function test.

• Object recognition: The cognitive function test is to recognize objects.

• Personal content: The cognitive function test is to identify non-text content the user provided to the website.

Example of a 3.3.8 failure: “I can never remember my password, it’s really hard to get into this app.”

Meet New Accessibility Standards Faster with AudioEye

Staying compliant with WCAG 2.2 doesn’t have to be overwhelming. AudioEye’s Accessibility Platform combines powerful automation with human-assisted AI technology to help you achieve industry-leading compliance with accessibility standards. From our free Website Accessibility Checker to our Expert Audits performed by real users and members of the disability community, AudioEye simplifies and streamlines your path to WCAG conformance.

Ready to see how AudioEye keeps your digital experiences accessible and compliant? Get started with a free accessibility scan.

Want more information? Schedule a demo to learn more or to see our platform in action.