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

A foot in a white sneaker on the yellow tactile warning strip at the edge of a platform.
Tactile paving: accessibility designed into the place, not added afterwards.Photo: Zoshua Colah on Unsplash

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.

css
/* keep focused elements clear of a 72px sticky header and a cookie bar */
html {
  scroll-padding-top: 88px;
  scroll-padding-bottom: 120px;
}
Browsers use scroll padding when they scroll a focused element into view, so it clears a fixed header and a cookie bar at once.

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.
The W3C Web Accessibility Initiative’s introduction to web accessibility and the standards behind it. Played from youtube-nocookie.com.

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

  1. WCAG 2.2 becomes a W3C Recommendation

    Nine new success criteria; 4.1.1 Parsing is retired.

    Source 1W3C

  2. The European Accessibility Act applies in the EU

    Many consumer-facing products and services, e-commerce among them, must now be accessible.

    Source 6AccessibleEU (European Commission)

Sources. Where the facts come from.

Numbered as they are cited in the text. Each link opens the original.

  1. Web Content Accessibility Guidelines (WCAG) 2.2

    W3C · 5 October 2023 (current edition 12 December 2024)

    Back to the text

Review log

When this guide was checked against its sources, and what changed. Newest first.

  1. 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).

Tell us what you need built.

You will speak to a lead who would run the work, and get a straight answer on fit.

Book a call

Three ways to start

  1. 01About 2 minutes

    A quick question

    You get A reply from a named lead

  2. 02About 8 minutesRecommended

    A project brief

    You get Options and a first scope after one call

  3. 03About 15 minutes

    A formal RFQ or RFP

    You get Receipt confirmed and a named bid lead

Every engagement starts with a written scope and a quote agreed before work begins. How each package is priced