Talk to a person. We reply within one working day.

SEO and AI search
Web
AI
Resources
WorkAboutStart a project

Accessibility checklist

WCAG 2.2 accessibility checklist: what changed and how to test it

WCAG 2.2 keeps everything from 2.1 and adds new criteria for focus, dragging, target size, help and sign-in. Start with those, then run the fifteen-minute pass.

4 min read · By the Liftup team in Pune

Gātha, a project by Liftup Technologies
New enquiryfrom the contact form
Our work: Gātha

350+businesses served

8countries

7+years

  • Ajyal Al Mustakbal Education
  • APHERO
  • Bimble
  • D'Decor
  • Edunova
  • Emoticons India
  • Gatha
  • Improp
  • Interakt
  • Jai Ganesh Industries
  • Medicine Free Life
  • Premium Learnings
  • Serene Eco Village
  • Tata Tele Business Services
  • WTS Management

In short

To meet WCAG 2.2 level AA, keep the 2.1 requirements and add six new criteria: visible focus that is not hidden, a click alternative to dragging, targets of at least 24 by 24 CSS pixels, consistent help placement, no repeated data entry, and sign-in that does not depend on memory tests.

Rather have it done for you? See our website maintenance service, plans from $120 a month.

On this page 6 sections
  1. What WCAG 2.2 adds
  2. The fifteen-minute manual pass
  3. Content and design checks
  4. Forms and errors
  5. Why it matters beyond ethics
  6. Our notes and the download

What WCAG 2.2 adds

CriterionLevelWhat it asksQuick test
2.4.11 Focus not obscured (minimum)AAA focused item is not fully hidden behind sticky headers, banners or chat widgetsTab through the page with a sticky header and a cookie bar showing
2.5.7 Dragging movementsAAAnything done by dragging can also be done with a simple click or tapTry sliders, reordering and maps without dragging
2.5.8 Target size (minimum)AAPointer targets are at least 24 by 24 CSS pixels, or have enough spacingInspect small icons, close buttons and inline links in lists
3.2.6 Consistent helpAHelp links or contact options sit in the same place on every pageCompare header and footer across five templates
3.3.7 Redundant entryAPeople are not asked to type the same information again in one processWalk through checkout and look for repeated address or email fields
3.3.8 Accessible authentication (minimum)AASign-in does not rely on remembering or transcribing, unless there is an alternativeCheck that password managers and paste both work

WCAG 2.2 also removes 4.1.1 Parsing, because modern browsers handle most markup errors. Level AA is the usual target for legal and procurement purposes.

The fifteen-minute manual pass

  1. Unplug the mouseTab through your home page, a product or service page and a form. Every control should be reachable, in a sensible order, with a visible focus outline.
  2. Zoom to 200%, then to 400%Content should reflow into one column at a width of 320 CSS pixels without sideways scrolling or hidden controls.
  3. Check contrastBody text needs a ratio of at least 4.5 to 1. Large text and interface parts such as input borders need 3 to 1.
  4. Turn on a screen readerUse VoiceOver on a Mac or NVDA on Windows. Listen to headings, links and one form. Do links make sense out of context?
  5. Turn off animationSet the system to reduce motion. Autoplaying carousels and parallax should stop or calm down.

Automated tools catch only some problems. Use them to find the easy ones, then do this pass by hand.

A longer explanation is on our page about a website accessibility checklist.

Free · no obligation

Get a free SEO and AI visibility check of your site

We look at how Google and AI tools like ChatGPT see your site and send you the top fixes, within one working day.

Content and design checks

  • One h1 per page, and headings that describe the structure rather than style the text
  • Every informative image has alt text. Decorative images have an empty alt attribute.
  • Link text says where it goes. 'Read more' repeated ten times does not.
  • Color is never the only way to show an error, a required field or a selected state
  • Videos have captions, and audio-only content has a transcript
  • The page language is set in the HTML, and any change of language inside the page is marked
  • Tables used for data have header cells, and layouts do not use tables
  • Text can be resized and spaced out without clipping

Forms and errors

  • Every field has a visible label tied to it in the code, not placeholder text alone
  • Required fields are marked in text, not only with a red asterisk
  • Errors appear next to the field, name the problem and say how to fix it
  • Autocomplete attributes are set for name, email, address and similar fields
  • A multi-step form remembers earlier answers (3.3.7)
  • Login allows paste and password managers, and CAPTCHA has a non-puzzle alternative (3.3.8)
  • Timeouts warn the user and let them extend the time

Why it matters beyond ethics

The European Accessibility Act began to apply to many consumer-facing products and services, including ecommerce, from 28 June 2025. In the US, website accessibility lawsuits often cite WCAG. In the UK, the Equality Act 2010 requires reasonable adjustments, and Australia's Disability Discrimination Act works the same way. None of these laws names a single checklist for every case, but WCAG AA is what most auditors and buyers use.

Accessible sites are also easier to use on phones, in bright light and with one hand. These fixes help everyone.

Our notes and the download

  • Build accessible components once. Retrofitting a finished design costs more than getting it right in the first sprint.
  • Test with sticky headers and cookie banners switched on. That is where the 2.4.11 failures hide.
  • Keep a short accessibility statement that says what you tested, what is known to fail and how to reach you.

The downloadable list has a pass or fail column for each criterion and our notes on common fixes. We build this into website design from the start.

Accessibility is one part of a full site check. The website audit checklist beyond SEO covers the rest.

Updated 20 November 2026

Questions, answered

Something else on your mind? Ask us directly or WhatsApp us. We reply within one working day.

Which WCAG level should my site meet?
Level AA is the normal target. Level A alone leaves out too much, and AAA is not expected for whole sites because some criteria cannot be met for all content.
Is WCAG 2.2 required by law?
Laws usually point to WCAG as a standard or to an equivalent, and the version they cite varies. Building to 2.2 AA also satisfies the 2.1 and 2.0 AA criteria, so it is the safe choice.
Can an accessibility overlay fix my site?
Overlays do not repair the underlying code, and many users with assistive technology find them intrusive. Fixing the templates is the dependable route.
How often should I test?
Before launch, after every major design or template change, and on a schedule such as twice a year. New plugins and embeds often introduce regressions.
Do PDFs need to be accessible too?
Yes, if people need them to use your service. Tag the headings, set the language, add alt text to images and check the reading order.

See your new homepage before you commit.

A free, private homepage concept built from your own words and photos within 48 hours.

Get a free concept