WCAG 2.2: What Changed and What It Means for Your Site

The Web Content Accessibility Guidelines (WCAG) are the main international standard for accessible websites. Version 2.2 became a W3C Recommendation in October 2023. It builds on 2.1, keeping everything in it (with one removal), and adds new success criteria that focus on people with cognitive and learning disabilities, low vision, and motor disabilities.

The basics

WCAG organizes requirements into three levels: A, AA, and AAA. Most laws and policies point to Level AA. Newer versions are designed to be backward-compatible, so a site that meets 2.2 AA also meets 2.1 AA and 2.0 AA, apart from one removed item.

What's new at A and AA

Focus Not Obscured (Minimum) — AA

When an element receives keyboard focus, it shouldn't be entirely hidden by other content. Sticky headers, cookie banners, and chat widgets are common culprits. See keyboard navigation and focus and how to design a website header.

Dragging Movements — AA

If something can be done by dragging, such as a slider or sortable list, there must also be a way to do it without dragging, for example with buttons or a single click.

Target Size (Minimum) — AA

Interactive targets should be at least 24 by 24 CSS pixels, with exceptions such as adequate spacing, inline links in text, or controls that are essential in a particular size. A larger size of 44 by 44 is commonly recommended for touch. See touch target sizes.

Consistent Help — A

If you provide help options, such as a contact link, chat, or phone number, place them in a consistent location across pages.

Redundant Entry — A

Don't make people re-enter information they've already given in the same process, unless it's essential or for security. Auto-fill or pre-populate where possible. See how to reduce form abandonment.

Accessible Authentication (Minimum) — AA

Logging in shouldn't depend on a cognitive function test, such as remembering a password or solving a puzzle, unless an alternative or assistance is available. Allow password managers and pasting, and offer alternatives such as email links or biometrics. See password managers for small teams.

New at AAA

WCAG 2.2 also adds Level AAA criteria, including Focus Not Obscured (Enhanced), Focus Appearance, and Accessible Authentication (Enhanced). Few sites aim for full AAA, but some are useful goals.

What was removed

Success criterion 4.1.1 Parsing was removed because modern browsers and assistive technologies handle most parsing problems themselves. You still should write valid, clean HTML.

What to do now

1. Check your sticky elements. Tab through pages and make sure the focused item remains visible.
2. Review small targets. Enlarge or space out tiny icons and links.
3. Provide alternatives to dragging.
4. Make help consistent. Keep your contact options in the same place.
5. Avoid asking for the same data twice.
6. Make login friendly to password managers and alternatives.
7. Keep the older basics in place: contrast, alt text, labels, headings, captions. See website accessibility basics.

Legal context

Many laws refer to WCAG, though the specific version and level vary by country and sector. See accessibility laws for small business websites. This is general information, not legal advice.

The bottom line

WCAG 2.2 adds practical requirements around focus visibility, target size, dragging, consistent help, redundant entry, and login. Fixing them also makes your site easier for everyone.