Understanding and Implementing WCAG 2.2 – the Standard for Accessible Websites
WCAG 2.2 is the internationally authoritative guideline for digital accessibility and the technical foundation behind the requirements of the BFSG and the European Accessibility Act. Find out which success criteria are new, what conformance levels A, AA, and AAA mean, and how to implement WCAG 2.2 on your website in a structured way.
The Key Facts at a Glance
WCAG 2.2 at a Glance
These four points summarize what WCAG 2.2 covers and why it matters for your website.
-
Current international W3C standard, published in October 2023
-
Four principles: perceivable, operable, understandable, robust
-
Three conformance levels: A (minimum), AA (legal standard), AAA (highest)
-
Technical basis of EU standard EN 301 549 – and therefore of the BFSG and EAA
Adds nine new success criteria to WCAG 2.1
Backward-compatible with WCAG 2.1 and WCAG 2.0
A globally recognized standard, also outside the EU
The basis for audits and conformance statements
What Is WCAG 2.2? Definition and Context
The Web Content Accessibility Guidelines 2.2 (WCAG 2.2) are the current international standard from the W3C's Web Accessibility Initiative (WAI) and were published as an official W3C Recommendation in October 2023. They define testable success criteria for how web content must be designed so it is accessible and usable for as many people as possible – regardless of vision, motor impairments, hearing loss, or cognitive disabilities.
WCAG 2.2 extends the earlier versions WCAG 2.0 (2008) and WCAG 2.1 (2018) with nine additional success criteria and is backward-compatible: meeting WCAG 2.2 automatically means meeting WCAG 2.1 and 2.0 as well.
Why WCAG 2.2 matters for you:
-
Legal basis: the BFSG references WCAG 2.2 via EN 301 549
-
Conformance benchmark used by authorities, auditors, and reviewers
-
Internationally recognized – the basis of laws worldwide
The Conformance Levels of WCAG 2.2: A, AA, and AAA
WCAG 2.2 divides its success criteria into three conformance levels. These levels indicate how comprehensively a website implements accessibility – and how much effort is required to achieve it. Which level is legally required depends on the specific use case.
For companies covered by the Accessibility Strengthening Act, conformance level AA is typically the benchmark to meet. This level is also the basis of the EU standard EN 301 549, which the BFSG references.
The Three Conformance Levels in Detail
Level A – Minimum
Removes fundamental barriers. Without level A, a website is barely usable for many user groups – for example keyboard use or alt text for images.
Level AA – Standard
The required standard for most legal requirements in the EU, including the BFSG and EAA. Includes sufficient contrast ratios and responsive display, among other things.
Level AAA – Highest
Maximum accessibility. Due to sometimes very strict requirements, often not achievable for every content type – but worthwhile for particularly sensitive areas.
The Four Principles of WCAG 2.2
WCAG 2.2 structures its requirements around four overarching principles, known by the acronym POUR: Perceivable, Operable, Understandable, Robust. Every WCAG 2.2 success criterion maps to exactly one of these principles.
If you want to understand WCAG 2.2, start here:
1. Perceivable
Content must be perceivable by all users – visually, audibly, or via assistive technologies. In practice, this means meaningful alt text for images, captions and transcripts for audio and video content, and sufficient color contrast. Information must never be conveyed through color alone.
2. Operable
All functions must be accessible without a mouse. WCAG 2.2 requires full keyboard operability, visible focus indicators, sufficient time for input, and avoiding content that could trigger seizures – for example through strong flashing.
3. Understandable
Content and interaction logic must be understandable. Clear language, unambiguous labels, predictable navigation, and helpful error messages with correction guidance are key requirements. Forms need explanatory hints and traceable validation.
4. Robust
Content must be interpretable by current and future technologies – particularly by screen readers and other assistive technologies. This requires clean, standards-compliant code, correctly marked-up ARIA attributes, and valid HTML.
The New Success Criteria in WCAG 2.2 at a Glance
With version 2.2, the W3C introduced nine new success criteria – with a particular focus on people with motor or cognitive impairments. Six of the nine core criteria fall under conformance level AA and are therefore directly relevant for BFSG implementation.
Focus Not Obscured (2.4.11, AA)
When an element receives keyboard focus, it must not be completely hidden by other content – such as a sticky header or cookie banner.
Dragging Movements (2.5.7, AA)
Functions that require dragging must also be operable through simple click or tap gestures – important for users with limited motor control.
Target Size (Minimum) (2.5.8, AA)
Click and touch targets must be at least 24x24 CSS pixels to be reliably hit – relevant for touchscreens and fine motor impairments.
Consistent Help (3.2.6, A)
Help features such as contact forms, FAQ links, or chat must be reachable in the same location across all pages.
Accessible Authentication (3.3.8, AA)
Login processes must not require cognitive tests, such as memorizing complex passwords or solving CAPTCHAs, without offering an alternative.
Redundant Entry (3.3.7, A)
Information already entered during a process – such as a delivery address – must not be requested again within the same process.
WCAG 2.2 and the BFSG: How Are They Connected?
The Accessibility Strengthening Act (BFSG) has required many companies to make their digital offerings accessible since 28 June 2025. However, the law itself does not define the specific technical requirements – it references the harmonized European standard EN 301 549, which in turn references WCAG 2.2 directly.
In practice, this means: meeting WCAG 2.2 at conformance level AA generally also meets the technical requirements of the BFSG and the European Accessibility Act. Full accessibility, however, only comes from consistent implementation in your website's code, structure, and content – a widget or a statement alone is not enough.
-
BFSG obligation since 28 June 2025 for online shops, banks, transport services, and more
-
EN 301 549 adopts WCAG 2.2 level AA as its technical benchmark
-
WCAG 2.2 provides the testable criteria for audits and conformance statements
Who Benefits from Implementing WCAG 2.2?
Accessible content under WCAG 2.2 is not a niche topic. Around 7.8 million people in Germany live with a severe disability – and many more are affected by temporary or age-related limitations. WCAG 2.2 helps ensure that these user groups can actually use your website.
These User Groups Benefit Directly
Blind and Low-Vision Users
Rely on alt text, correct structure, and compatible screen reader support.
Users with Motor Impairments
Use a keyboard, voice control, or specialized input devices – instead of a mouse or precise touch gestures.
Deaf and Hard-of-Hearing Users
Need captions, transcripts, and visual alternatives to audio content.
Users with Cognitive Disabilities
Benefit from plain language, clear structure, and predictable interaction patterns.
Older and Situationally Limited Users
Benefit directly too – for example in bright sunlight on a screen, or when using a device one-handed on the go.
Frequently Asked Questions About WCAG 2.2
A complete WCAG 2.2 review combines automated testing, manual audits, and user testing. Automated tools such as SiteCockpit's easyMonitoring reliably detect a large share of technical violations and prioritize the findings. Certain criteria – such as the understandability of content – additionally require manual evaluation by specialists.