
WCAG 2.2: guidelines, levels and new criteria explained
8 min read below · WebYes knowledge base
Last updated:
What changed: Section on WCAG 2.1 and 2.2 rewritten with the six new A/AA criteria; 2.1 AA named as the current legal version; caveat on 4.1.1 added; unsourced coverage claim removed.
What is WCAG 2.2, what is new compared to 2.1 and which version does the law require now? Levels A, AA, AAA, the six new A/AA criteria and how to test.
WCAG is the international standard for accessible websites, maintained by the W3C. Version 2.2 (December 2024) adds requirements on focus, dragging, target size and signing in. Through EN 301 549 the law currently refers to WCAG 2.1 AA; 2.2 AA is expected to become the legal yardstick in 2026.
The four principles of the WCAG guidelines
WCAG (Web Content Accessibility Guidelines) is the international standard for accessible websites and apps, maintained by the W3C. The guidelines rest on four principles and three levels. Dutch and European rules refer to level AA through the standard EN 301 549; in the current version of that standard this is WCAG 2.1. The newest version, WCAG 2.2, has been the current W3C recommendation since December 2024 and is expected to become the legal yardstick during 2026 as well. WebYes tests automatically against WCAG 2.2 AA; part of the criteria always needs a human judgement. Want to see first what your site shows automatically? See which WCAG failures your site shows automatically with a free scan.
All criteria in WCAG 2.2 fall under four principles. The WCAG guidelines are built so each principle asks a clear question. Perceivable: information must be visible or audible to everyone, for instance through alt texts on images and captions on video. Operable: every function must also work without a mouse, using a keyboard or voice control. Understandable: copy, navigation and error messages must be clear. Robust: the site must work well with different browsers and assistive technology, such as screen readers.
Each principle is broken down into concrete success criteria. Think of a minimum contrast ratio of 4.5:1 for normal text, a visible focus indicator during keyboard navigation, form fields with an associated label, and touch targets large enough to hit with a thumb. Working through these criteria systematically does not only solve 'compliance'; it also removes friction that every visitor feels on phone and desktop.
The principles are deliberately technology-agnostic. Whether you build a classic HTML site, a single-page app or a native webview: the question remains whether someone with an impairment can complete the task. That makes the WCAG guidelines a stable yardstick across design, development and periodic scans.
Levels A, AA and AAA
WCAG has three levels. Level A covers the absolute basics; without those criteria a site is unusable for some groups. Level AA is the legal and practical norm for governments and, through the European Accessibility Act, for many commercial services. Level AAA is the strictest level and rarely fully achievable for an entire site; it fits better for specific components or audiences.
| Level | What it means | When it matters |
|---|---|---|
| A | Minimal accessibility, removes the worst barriers | Always, for every website |
| AA | The practical norm: contrast, navigation, forms | Legal requirement for government and many businesses |
| AAA | Strictest requirements, such as sign language for video | Specific audiences or components |
For e-commerce services, regulator ACM names WCAG 2.1 level AA as the current requirement: all criteria of level A and AA. AAA is not the legal default; only promise it if you can truly deliver that part.
WCAG 2.1 or 2.2: which version should you use?
WCAG 2.2 builds on 2.1 and adds nine success criteria. Six of them fall under level A or AA and therefore count toward the practical norm. The W3C describes them in the WCAG 2.2 recommendation of 12 December 2024.
| Criterion | Level | In short |
|---|---|---|
| 2.4.11 Focus Not Obscured (Minimum) | AA | An element with keyboard focus must not be entirely hidden behind, for example, a sticky header or cookie bar. |
| 2.5.7 Dragging Movements | AA | Anything that works by dragging must also work with a single click or tap. |
| 2.5.8 Target Size (Minimum) | AA | Click and tap targets at least 24 × 24 CSS pixels, or enough space around them. |
| 3.2.6 Consistent Help | A | Help (contact, chat, FAQ) that appears on several pages sits in the same place in the order each time. |
| 3.3.7 Redundant Entry | A | Do not make people type information again that they already gave in the same process. |
| 3.3.8 Accessible Authentication (Minimum) | AA | Signing in without a memory or puzzle test, or with help such as pasting and password managers. |
In addition, criterion 4.1.1 (Parsing) was removed in 2.2, because assistive technology no longer needs to parse HTML itself. The W3C states that content that conforms to 2.2 also conforms to 2.0 and 2.1; if you formally have to report against 2.1, you may still need to include 4.1.1.
Which version should you choose? The ACM names WCAG 2.1 AA as the current requirement for e-commerce services and advises working with 2.2 already; Digitoegankelijk expects a new EN 301 549 referring to 2.2 at the end of 2026. If you build or rebuild now, test against 2.2 AA: that covers 2.1 and you will not have to start over later. What the law asks of web shops is explained on our page on the European Accessibility Act.
Overlap with target size on mobile is largest here. Criteria on target size and focus are exactly the failures that hurt on phones. Taking 2.2 AA seriously often makes the site nicer to use on mobile at the same time.
WCAG, EN 301 549 and the legal context
WCAG itself is a technical standard, not a law. Dutch and European rules refer to it. Public bodies fall under the government accessibility decree; Digitoegankelijk describes who that covers. For businesses the European Accessibility Act has applied since 28 June 2025 to e-commerce services among others; see that page for the legal details and exemptions.
According to the ACM, that duty applies to providers with 10 or more employees or annual turnover above 2 million euros. Micro-enterprises below both thresholds are exempt. The technical yardstick is WCAG level AA (via EN 301 549), currently in version 2.1. A quality mark is not legally required; the law demands that your service is accessible, not that you display a sticker.
Alongside the technical check, public status documentation often applies. Governments and many e-commerce services must publish an accessibility statement; that page explains when it is required and what it must cover. For the broader explanation of duties and a practical approach, see digital accessibility. This page stays on the technical depth: what WCAG is, how the levels work, and how you test.
How to test, and what WebYes finds automatically
Automated tools find the measurable problems: missing alt texts, contrast errors, empty buttons, missing labels and errors in the HTML structure. That is the fastest way to surface the biggest issues. A full WCAG audit also requires manual research, because criteria such as understandable error messages and a logical reading order cannot be judged by a machine. Part of the success criteria can be checked reliably by a tool; for the rest, such as whether an alt text is accurate or an error message understandable, a person is needed.
WebYes runs automated WCAG 2.2 AA checks within the accessibility pillar, alongside speed, security and mobile. The free scan covers up to six pages; a full audit up to fifteen, sitemap-led. The quality mark requires an average score of at least 80 and at least 60 per pillar: a strong speed score does not compensate for systematic a11y failures.
A practical approach: measure where you stand first, fix the blockers (labels, contrast, empty buttons, keyboard traps), then walk through the key tasks (ordering, contacting, logging in) manually with a keyboard and screen reader. Repeat after major releases. Accessibility is not a one-off project; every new feature can introduce new barriers. Document what you still need to test manually beside the scan, so you do not confuse a good scan score with full AA conformity.
Sources
Frequently asked questions
What are the WCAG guidelines exactly?
The WCAG guidelines are the Web Content Accessibility Guidelines from the W3C: a set of success criteria under four principles (perceivable, operable, understandable, robust) with levels A, AA and AAA. In the Netherlands and the EU, level AA is the practical norm that legislation refers to. Version 2.2 is the current recommendation.
Is WCAG legally required?
WCAG itself is a technical standard, not a law. But Dutch and European legislation refers to it: governments must meet WCAG level AA, and through the European Accessibility Act the same applies to many web shops and online services (ACM: 10+ employees or more than 2 million euros turnover). In practice, WCAG AA is the legal yardstick; in the current version of EN 301 549 that is WCAG 2.1.
How many WCAG criteria can an automated scan test?
Not all of them. Criteria such as contrast, missing labels or alt attributes are easy to measure automatically. Whether an alt text conveys the right meaning, or a form is logically built, needs human judgement. Treat the scan as a starting point, not a verdict.
Which WCAG version is legally required now?
For governments and e-commerce services the law currently refers to WCAG 2.1 AA through EN 301 549. WCAG 2.2 AA is expected to become the new standard during 2026.
What is the difference between WCAG and EN 301 549?
EN 301 549 is the European standard for ICT accessibility and covers apps, documents and hardware in addition to websites. For web content, EN 301 549 refers directly to the WCAG criteria. If you meet WCAG AA, your website meets the relevant part of EN 301 549.
Which WCAG version does the WebYes scan use?
WebYes tests automatically against WCAG 2.2 AA within the accessibility pillar. The quality mark requires an average of at least 80 and at least 60 per pillar; free scan up to six pages, full audit up to fifteen.
The WebYes scan measures this too
Scan your website for free on speed, security, mobile and accessibility and see where you stand.
Start free scan


