In October 2023, the Web Content Accessibility Guidelines (WCAG) were updated to version 2.2. With this update, developers and technical teams must prepare for a new set of accessibility requirements. While WCAG 2.1 laid the foundation, 2.2 introduces success criteria that target cognitive, motor, and usability challenges. If you build or maintain websites, these updates directly impact how your digital experiences perform for users and whether they meet legal standards. Familiarize yourself with the seven key changes in WCAG 2.2 so you can plan for your sites.

Keep focused elements fully visible

Ensure that interactive elements retain visible focus when tabbed into view. Avoid overlaps from sticky headers or modals. This improves keyboard navigation and supports visible orientation.

Provide non-drag alternatives

Provide non-drag alternatives for drag-and-drop interfaces. Users must be able to complete tasks with simple taps or clicks. Consider keyboard-accessible options.

Increase the tap area size

Touch targets must be at least 24x24 pixels or appropriately spaced to prevent accidental clicks. This is especially relevant for mobile-first development.

Standardize the help element placement

Any form of help, like a live chat or a support link, should be consistently positioned across your site. Developers should avoid placing these elements in varying locations between pages.

Simplify login authentication

Forms must allow users to log in without relying solely on cognitive tests, such as puzzles or remembering passwords. Developers can support this through password managers, device biometrics, or email- or SMS-based logins.

Prevent redundant data entry

Avoid requiring users to re-enter data that was previously submitted unless absolutely necessary. Use autofill or smart session management where possible.

Improve the focus indicator design

Focus indicators must now meet a contrast ratio of at least 3:1 and have a visible border or outline of 2 pixels. Review your CSS to ensure WCAG-compliant styling.

For developers, staying compliant with WCAG 2.2 means auditing existing codebases, updating design tokens, and revisiting user flows. An accessibility app supports AA- and AAA-level compliance using an autofix solution, helping technical teams streamline updates with minimal development time.