Guide4 min readProduct & Experience Design · Technology & Intelligence
WCAG 2.2 for marketing sites: the nine new criteria, in plain terms
WCAG 2.2 added nine success criteria, six at the A and AA levels most contracts ask for. What each means for banners, forms and sign-in, and how to fix them.
Xterra EdzeEditorial
Published Reviewed

The Web Content Accessibility Guidelines sit behind most accessibility law and procurement checklists. Version 2.2 became a W3C Recommendation on 5 October 2023. It keeps everything in 2.1, adds nine success criteria and removes one, 4.1.1 Parsing, which modern browsers had made obsolete.1 2 Most new criteria help keyboard users, people with limited dexterity and people with cognitive disabilities. On marketing sites, most failures we find come from a handful of familiar components.
- New success criteria in WCAG 2.2
- 9
- Of them at levels A and AA
- 6
- Four at AA, two at A. The other three are AAA.
- CSS pixels: the minimum target size at AA
- 24 × 24
- Or enough spacing around a smaller target.
Source: What’s New in WCAG 2.2, W3C Web Accessibility Initiative.
The six at levels A and AA
2.4.11 Focus Not Obscured (Minimum) · AA
When an element receives keyboard focus, it must not be entirely hidden by content the author created.3 The usual culprits are sticky headers, chat launchers and cookie banners covering the link a keyboard user has tabbed to. Scroll padding equal to the sticky header’s height fixes most cases; banners should leave room for the content they would otherwise cover.
/* keep focused elements clear of a 72px sticky header and a cookie bar */
html {
scroll-padding-top: 88px;
scroll-padding-bottom: 120px;
}2.5.7 Dragging Movements · AA
Anything that works by dragging needs a single-pointer alternative, unless dragging is essential.2 Swipe-only carousels, drag-to-reorder lists and sliders without buttons or an input all need a way to do the same with taps or clicks.
2.5.8 Target Size (Minimum) · AA
Pointer targets must be at least 24 by 24 CSS pixels, or spaced so that a 24-pixel circle centred on each does not touch another target. Links inside a sentence and controls the browser draws itself are exempt.4 This usually fails on footer link lists, social icons and close buttons. On our own sites, standalone tap targets are 44 pixels on phones, which clears the criterion comfortably.
3.2.6 Consistent Help · A
If help is offered on several pages (a contact link, phone number, chat or help centre), it must appear in the same relative order each time.2 Put it in the shared header or footer and leave it there.
3.3.7 Redundant Entry · A
In a multi-step process, do not ask again for information the person has already given. Fill it in or let them select it, unless re-entering it is essential or needed for security, or the earlier answer is no longer valid.2 Shipping and billing addresses are the classic case.
3.3.8 Accessible Authentication (Minimum) · AA
Signing in must not depend on a cognitive function test, such as remembering a password, solving a puzzle or transcribing characters. Exceptions apply when there is an alternative or a mechanism that helps, or when the test is recognising objects or the person’s own content.5 Allow paste and password managers in password and code fields, and offer passkeys or an emailed link where you can.
The three at AAA
- 2.4.12 Focus Not Obscured (Enhanced): no part of the focused element is hidden by author content.
- 2.4.13 Focus Appearance: the focus indicator meets a minimum size and contrast against its unfocused state.
- 3.3.9 Accessible Authentication (Enhanced): no cognitive function test at all, without the object-recognition and personal-content exceptions.
Why it matters beyond a checklist
Accessible sites are easier for everyone to use. Bigger targets, visible focus and forms that remember what you typed also help someone on a train with one hand free. The law is moving too. In the EU, the European Accessibility Act has applied since 28 June 2025 to many consumer-facing products and services, including e-commerce.6 Building to WCAG 2.2 AA from the first sprint costs far less than retrofitting a launched site.
- Tab through every template with the sticky header and the cookie banner showing.
- Measure footer links, icon buttons and close buttons against 24 by 24 pixels.
- Operate every carousel, slider and map with single clicks only.
- Fill each multi-step form and note anything you are asked twice.
- Sign in with a password manager, and paste a one-time code.
We build to WCAG 2.2 AA by default in Experience Design & Development, and audit existing sites against it in Audits & Assessments.
Key dates this guide tracks.
The changes this guide covers, in date order, each with its source. See every date in the standards timeline
Sources. Where the facts come from.
Numbered as they are cited in the text. Each link opens the original.
-
Web Content Accessibility Guidelines (WCAG) 2.2
W3C · 5 October 2023 (current edition 12 December 2024)
-
W3C Web Accessibility Initiative
Back to the text:Back to the text, place 1Back to the text, place 2Back to the text, place 3Back to the text, place 4
-
Understanding Success Criterion 2.4.11: Focus Not Obscured (Minimum)
W3C Web Accessibility Initiative
-
Understanding Success Criterion 2.5.8: Target Size (Minimum)
W3C Web Accessibility Initiative
-
Understanding Success Criterion 3.3.8: Accessible Authentication (Minimum)
W3C Web Accessibility Initiative
-
A new era for inclusion begins: the European Accessibility Act enters into force
AccessibleEU (European Commission) · June 2025
Review log
When this guide was checked against its sources, and what changed. Newest first.
Checked the nine new criteria, their levels and the retirement of 4.1.1 Parsing against the current edition of WCAG 2.2 (12 December 2024).





