Website & Development
WCAG 2.1 AA Explained: A Checklist for Marketing Teams (and What 2.2 Adds)
Copy for AI
A WCAG checklist turns the accessibility guidelines into checkpoints you can test yourself.
Does your text have enough contrast? Does everything work with the keyboard? Does a screen reader understand your forms?
The verdict: test against WCAG 2.1 AA, the legal benchmark in Europe, but build towards WCAG 2.2 AA. That covers both.
Below you get what AA asks, who in your marketing team owns which criterion and a checklist per theme. You also see what audit tools such as WAVE and axe catch, and where manual testing stays indispensable.
What is WCAG 2.1 AA, and what does 2.2 add?
WCAG 2.1 AA is the set of 50 level A and AA success criteria a page must meet.
WCAG 2.1 was published on 5 June 2018 as a W3C Recommendation. It organises accessibility into 13 guidelines under four principles.
Three levels, one practical norm
Each guideline has testable success criteria at three levels:
- Level A: the absolute minimum.
- Level AA: all A and AA criteria together, 50 in WCAG 2.1.
- Level AAA: the strictest, often not achievable for a whole site.
AA is the practical norm: strict enough to be genuinely usable, realistic enough to sustain.
Why 2.1 AA is the legal benchmark
AA is also the level that counts for the European Accessibility Act. The European standard EN 301 549 incorporates WCAG 2.1 AA for web content.
Our explainer on the European Accessibility Act covers who has to comply.
What WCAG 2.2 changes
WCAG 2.2 is the current version, published on 5 October 2023. It contains 86 success criteria across levels A, AA and AAA. That’s the version to build towards.
Compared with 2.1, it added nine success criteria and removed the obsolete criterion 4.1.1 (parsing). The new ones that matter most at A and AA level:
| New in 2.2 | Level | What it means for a marketing site |
|---|---|---|
| 2.4.11 Focus Not Obscured (Minimum) | AA | A sticky header or cookie banner may not hide the focused element |
| 2.5.7 Dragging Movements | AA | Sliders and carousels also work without dragging |
| 2.5.8 Target Size (Minimum) | AA | Buttons and links are big enough to hit |
| 3.2.6 Consistent Help | A | Contact options sit in the same place on every page |
| 3.3.7 Redundant Entry | A | Forms don’t ask for the same information twice |
| 3.3.8 Accessible Authentication (Minimum) | AA | Logging in doesn’t depend on a memory or puzzle test |
The full list is on the W3C page What’s new in WCAG 2.2.
According to the W3C, “content that conforms to WCAG 2.2 also conforms to WCAG 2.1 and WCAG 2.0.” Build to 2.2 AA, and you’re also covered for the legal benchmark.
The four principles: POUR
The guidelines revolve around four principles. Content must be perceivable, operable, understandable and robust.
Those four words are a handy anchor when you’re unsure which category a problem falls under.
Who in your marketing team owns which criterion?
Usually not the developer alone, because most errors appear at the moment of publishing.
Accessibility often stalls because everyone assumes the developer will fix it. In reality the mistakes arrive with content: an image without alt text, a button in a campaign colour with too little contrast, a PDF nobody checked.
The owner table
This table links the WCAG 2.1 AA criteria that most often go wrong on marketing sites to the role that can prevent them:
| Criterion (WCAG 2.1) | What it asks | Owner |
|---|---|---|
| 1.1.1 Non-text content (A) | A text alternative for every meaningful image, chart or icon button | Content editors |
| 1.2.2 Captions (A) | Captions for video with speech | Content editors, video |
| 1.3.1 Info and relationships (A) | Headings, lists and tables in real HTML structure, not only visually | Developer, editors |
| 1.3.5 Identify input purpose (AA) | Fields such as name and email technically identifiable, so browsers can autofill them | Developer |
| 1.4.3 Contrast minimum (AA) | At least 4.5:1 for text, 3:1 for large text | Design, brand |
| 1.4.4 Resize text (AA) | Text enlargeable to 200% without loss of content | Design, developer |
| 1.4.10 Reflow (AA) | Usable at a width of 320 CSS pixels without horizontal scrolling | Design, developer |
| 1.4.11 Non-text contrast (AA) | At least 3:1 for buttons, input fields and graphical elements | Design |
| 2.1.1 Keyboard (A) | All functionality operable with the keyboard | Developer |
| 2.4.4 Link purpose (A) | Link text that says where you will end up | Content editors |
| 2.4.7 Focus visible (AA) | A visible focus indicator | Design, developer |
| 3.3.1 and 3.3.2 Errors and labels (A) | Clear labels, instructions and error messages in forms | Marketing, developer |
| 4.1.2 Name, role, value (A) | Buttons, menus and sliders that a screen reader names correctly | Developer |
You’ll find the criterion texts in the WCAG 2.1 specification.
Rule of thumb: give each role its own rules in your publishing process.
Then nobody needs to know the full standard by heart.
Which checkpoints are on the checklist?
Five themes cover the core of a WCAG 2.2 AA checklist.
Run through them page by page. Start with your most important templates: homepage, services page, contact page and blog article.
Where most sites fail
The WebAIM Million shows where to look first. In February 2026, 95.9% of one million home pages had detectable WCAG failures, with 56.1 errors per page on average (WebAIM Million).
The six most common failures:
So the 4.1% without detected errors weren’t automatically accessible either. Contrast tops the list, which is why it’s the first theme below.
Colour and contrast
Check these three points:
- Normal text has a contrast ratio of at least 4.5:1; large text at least 3:1.
- Colour is never the only signal: an error is red and has text or an icon.
- Buttons, links and form fields stay visible in focus and hover states.
For example, light grey body text on white often fails the 4.5:1 test. Our guide to a website colour palette shows how to pick brand colours that pass.
Text and structure
Headings and links need a logical order:
- One H1, then H2s and H3s, without skipping levels.
- Descriptive link text instead of stray “read more” links.
- Text that stays readable at 200 percent zoom, without overlap.
A clean heading order also helps search engines, as our guide to heading structure for SEO explains. Size and line spacing come back in our guide to website typography.
Images and media
Two checks per image and video:
- Content images have meaningful alt text; decorative ones get an empty alt.
- Videos with speech have captions.
Tip: write alt text for what the image proves, not for how it looks. Our piece on alt text for multimodal AI shows good and bad examples.
Keyboard and focus
Everything that works with the mouse must work with the keyboard alone:
- Tab, Enter and the arrow keys reach every function.
- The focus order is logical and the focus indicator always visible.
- There’s no keyboard trap: you can always navigate back out.
New in 2.2: a sticky header may not cover the focused element, even at the top of the page.
Forms
Forms are where accessibility touches your leads directly:
- Every field has a visible, linked label, not just a placeholder.
- Error messages say what went wrong and how to fix it.
- Buttons are large enough to hit comfortably on mobile.
A form that’s unclear to a screen reader user usually confuses a hurried visitor too.
Read more in our guide on form conversion optimisation and our tips for lead form optimization.
How do you test this with audit tools like WAVE and axe?
Start with an automated scan, because it finds a fair share of the technical errors in minutes.
Three free tools
Two widely used, free browser extensions do most of the work:
- WAVE: from WebAIM, shows errors and structure right on the page.
- axe DevTools: from Deque, lists issues inside the browser’s developer tools.
- Lighthouse: built into Chrome, gives an accessibility score.
How to read those Lighthouse reports is covered in our explainer on Google Lighthouse.
Here’s what a WAVE scan looks like on a live page:
What tools do well, and what they miss
What these tools catch:
- missing alt text and form labels
- contrast that’s too low
- a faulty heading structure
- a missing language setting
What they can’t judge: whether an alt text is substantively right, whether the focus order feels logical, or whether an error message is understandable.
WebAIM puts it plainly: “Absence of detected errors does not indicate that a page is accessible or conformant.”
That’s why the honest expectation is that automated tools catch roughly a third to a half of the problems. They’re a starting point, not a finish line.
A practical routine
Run WAVE or axe over your most important page types and fix the reported errors. Then use the warnings as a checklist for manual review.
Here’s the same check in axe DevTools:
Want a first picture without installing anything? Use our WCAG checker.
It tests your homepage, a product page and a form for automatically detectable WCAG errors.
Fix those first. Then test by hand.
Where is manual testing still needed?
Wherever the problem depends on context, because only a human can judge that.
The most impactful accessibility problems are contextual. Three checks you can do yourself without much expertise.
1. The keyboard test
Put your mouse aside and walk an important flow, for example from homepage to contact form, with only Tab, Shift+Tab and Enter.
Ask three questions:
- Can you reach everything?
- Do you always see where the focus is?
- Can you submit the form?
No? Then you’ve found a blocker that no scan picks up.
2. The screen reader test
Turn on a screen reader: VoiceOver on Mac, or NVDA on Windows, which is free. Have a page read aloud.
Do your links and buttons make sense out of context? Are images described meaningfully?
It feels awkward. But twenty minutes teaches you an enormous amount.
3. The zoom and mobile test
Zoom in to 200 percent and view the page on a narrow screen.
Does everything stay readable? Or does content drop out? Criterion 1.4.10 asks for a usable page at 320 CSS pixels wide.
When to bring in a specialist
For a full audit or a legally substantiated conformance report, bring in a specialised tester. Often that’s someone who uses assistive technology themselves.
For the errors that occur most often, read our rundown of web accessibility mistakes.
But you’ll pick most of the low-hanging fruit yourself.
Why is this relevant for B2B marketers?
Because accessibility helps your conversion and is increasingly a requirement.
The legal side
The European Accessibility Act has applied since 28 June 2025. It obliges a growing group of organisations to make their digital services accessible.
The law mainly targets consumer-facing products and services, such as e-commerce and banking. So not every pure B2B site falls within the strict legal scope.
But the direction is clear: accessibility is shifting from nice-to-have to standard expectation. For public institutions, an obligation has applied for longer.
How the law also affects your lead flow is covered in the European Accessibility Act and lead generation.
The lead side
More important for daily practice is the effect on leads.
What makes a site accessible makes it nicer for everyone: readable text, clear buttons, logical navigation and forms that go right the first time.
That’s what we focus on at Customer Impact: a site that turns visitors into requests, not vanity statistics. A logical, accessible menu supports that directly; see our guide on website navigation.
It belongs in the broader approach we describe in the B2B website guide and our UX best practices.
Frequently asked questions
What is the difference between WCAG 2.1 AA and WCAG 2.2 AA?
WCAG 2.2 adds nine criteria, including on the minimum size of click targets, focus that must not be hidden and easier login, and removes the obsolete criterion 4.1.1. Everything that meets 2.2 also meets 2.1.
Does my website have to meet WCAG 2.1 AA?
If your site falls under the European Accessibility Act, for example because consumers buy or book online, WCAG 2.1 AA is the benchmark in practice. A purely informational B2B site usually falls outside that obligation, but the same criteria do make your site more usable.
How many of the errors does an automated tool find?
Part of them. A tool reliably finds missing labels, alt attributes and contrast that is too low. Whether an alt text is right, whether the focus order is logical and whether an error message is understandable can only be judged by a person.
Do I also have to report my accessibility publicly?
Companies under the EAA must describe how their service meets the requirements. Many organisations do this with an accessibility statement; see our accessibility statement examples for what one looks like.
The short summary
WCAG 2.1 AA is the legal benchmark; WCAG 2.2 AA is the version to build towards.
Three steps get you most of the way:
- Divide the criteria between editors, design and development.
- Let WAVE or axe find the technical errors.
- Do the keyboard, screen reader and zoom test yourself.
Start with your most important page types and conversion points. That’s where accessibility pays off first.
Want your website reviewed for accessibility and conversion in one go? See our approach to WCAG compliance or contact us.
Free website scan
Enter your website and get an automatic scan within minutes, with concrete technical and SEO improvements. No sales pitch.
We only use your details for your scan. No spam, unsubscribe anytime.