WCAG 2.2 Level AA Standards and Key Changes

The WCAG framework is developed by the World Wide Web Consortium (W3C) Web Accessibility Initiative (WAI) to establish a single, shared standard for web content accessibility. The framework is organized into three levels of conformance: Level A (minimum accessibility), Level AA (the standard target for most legal compliance structures), and Level AAA (advanced accessibility).

The transition from WCAG 2.1 (published in 2018) to WCAG 2.2 (finalized in late 2023) represents an expansion of the guidelines to address specific user groups. The updates primarily focus on improving digital interfaces for individuals with cognitive or learning limitations, low vision, and physical disabilities that affect motor control, particularly when using mobile devices.

Unlike some software updates, WCAG 2.2 does not overwrite the previous version. Instead, it builds directly on top of the criteria established in WCAG 2.1. One notable structural change is the removal of Success Criterion 4.1.1 (Parsing). This criterion was declared obsolete because modern web browsers and assistive technologies now handle HTML parsing errors consistently, making a dedicated coding standard for syntax parsing unnecessary.

The WCAG 2.2 update introduces nine new success criteria. For IT providers, software engineers, and quality assurance teams, understanding the technical implementation of these standards is essential for maintaining client compliance.

1. Focus Appearance (Success Criterion 2.4.11, Level AA)

This criterion establishes strict visual specifications for keyboard focus indicators. When a user tabs to an interactive element (such as a link, button, or form field), the focus indicator must meet two technical requirements:

• Contrast: The indicator must have a contrast ratio of at least 3:1 between the pixels of the indicator and the surrounding background.
• Area: The indicator must be of a minimum size, defined as an area at least equal to a 2 CSS pixel thick outline around the perimeter of the focused element.

Developers can satisfy this requirement by avoiding default browser outlines, which often fail contrast checks. Writing custom CSS focus states ensures that the indicator remains highly visible across all backgrounds. An effective custom outline utilizes a contrasting border:

a:focus-visible { outline: 2px solid #005a9c; outline-offset: 2px; }

This declaration guarantees that the focus ring is separated from the element’s border, meeting the necessary visibility area requirements.

2. Target Size Minimum (Success Criterion 2.5.8, Level AA)

To assist users with motor limitations or those using touchscreens, this criterion requires that all interactive targets have a minimum size or spacing. The target area must be at least 24 by 24 CSS pixels. If a target is smaller (such as a close icon or inline link), it must have sufficient empty space (padding) around it so that a 24-pixel diameter circle centered on the target does not overlap with any other target or spacing element.

A common implementation technique involves using CSS padding rather than margin to increase the target area of small icons. When layout items are placed close together, developers can utilize CSS Grid or Flexbox with a gap property to enforce spacing:

.toolbar-buttons { display: flex; gap: 12px; }

This ensures that even if individual button icons are small, the gap between their click thresholds prevents accidental activations, satisfying the spacing exception of the guideline.

3. Dragging Movements (Success Criterion 2.5.7, Level AA)

Any user interface feature that requires a dragging motion (such as a custom price slider, a map panning interface, or a kanban board) must also support a single-pointer alternative. A dragging movement can be difficult or impossible for individuals with limited manual dexterity.

Developers must ensure that users can achieve the same result using a simple tap or click. For a slider, this means adding plus and minus buttons that adjust the value incrementally when clicked.

4. Redundant Entry (Success Criterion 3.3.7, Level A)

This standard reduces cognitive load during multi-step forms, such as eCommerce checkout funnels or registration processes. If an application requires a user to enter information that they have already provided in a previous step, the application must auto-populate the fields or offer a single-click option to copy the data (such as a checkbox stating “billing address same as shipping”).

5. Accessible Authentication Minimum (Success Criterion 3.3.8, Level AA)

Login processes must not rely on cognitive function tests unless an alternative, accessible path is provided. A cognitive function test includes tasks such as memorizing a password, solving a math equation, transcribing characters from an image, or identifying patterns.

To meet this standard, login forms must support the copy-and-paste function, allowing users to utilize third-party password managers. Additionally, integration with OAuth providers (such as Google or Microsoft logins) or WebAuthn standards (such as facial recognition or fingerprint readers) provides compliant authentication pathways.

Integrating these new criteria into the development lifecycle requires updates to existing quality assurance workflows. Technical teams cannot rely solely on automated accessibility scanners, as many of these new standards (such as verifying single-pointer alternatives for dragging movements or evaluating cognitive login barriers) require human judgment.

QA engineers must establish manual testing checklists. These lists include verifying focus indicators using browser developer tools, measuring click targets in CSS pixels, and performing keyboard-only navigation tests. To prevent integration errors, designers and developers can align their templates with the updated guidelines by using structured website accessibility compliance testing procedures.

Adopting these validation steps early in the design phase prevents expensive remediation cycles post-release, ensuring that application launches meet current legal expectations and support all users.