{"id":992288,"date":"2026-05-25T15:24:35","date_gmt":"2026-05-25T15:24:35","guid":{"rendered":"https:\/\/ifdb.io\/wcag-2-2\/"},"modified":"2026-10-12T09:36:35","modified_gmt":"2026-10-12T09:36:35","slug":"wcag-2-2","status":"publish","type":"page","link":"https:\/\/ifdb.io\/en\/wcag-2-2\/","title":{"rendered":"WCAG 2.2"},"content":{"rendered":"\t\t
\n\t\t\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t\t
DIGITAL ACCESSIBILITY \u00b7 WEB STANDARDS \u00b7 BFSG \u00b7 EAA \u00b7 EN 301 549<\/h6>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

\nWCAG 2.2<\/span>\n \u2013 the web standard that makes digital accessibility verifiable in the first place.<\/span><\/h1>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

WCAG 2.2 forms the technical core of almost every accessibility regulation in Europe. Whether it\u2019s the BFSG, the European Accessibility Act or the EN 301 549 standard \u2013 ultimately, they all refer to the W3C\u2019s Web Content Accessibility Guidelines. Anyone who understands what WCAG 2.2 requires understands what a website is actually assessed against. On this page, we explain in simple terms what has changed in version 2.2, which new criteria have been added and how you can provide robust evidence of compliance. <\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\tBook a Demo<\/span>\n\t\t\t\t\t<\/span>\n\t\t\t\t\t<\/a>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\tStart Access Score\u00ae<\/span>\n\t\t\t\t\t<\/span>\n\t\t\t\t\t<\/a>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t
Trusted by leading companies across the DACH region
Featured as an expert on ZDF WISO<\/h6>\t\t\t\t<\/div>\n\t\t
\n\t\t
\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

\"Logo<\/span><\/span>\"Logo<\/span><\/span>\"Logo<\/span><\/span>\"Logo<\/span><\/span>\"Logo<\/span><\/span>\"Logo<\/span><\/span>\"Logo<\/span><\/span>\"Logo<\/span><\/span>\"Logo<\/span><\/span>\"Logo<\/span><\/span>\"Logo<\/span><\/span><\/h2><\/div>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t\t

What the WCAG 2.2 are and why they set the standard for everything else<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The WCAG, which stands for Web Content Accessibility Guidelines, are the internationally recognised guidelines for accessible web content, published by the World Wide Web Consortium (W3C). They are based on four fundamental principles: content must be perceivable, operable, understandable and robust \u2013 known in technical terms as the POUR model. <\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

The WCAG recognises three levels of compliance: A as the minimum, AA as the standard relevant to most websites, and AAA as the highest level. For legal compliance in Europe, Level AA is generally the decisive benchmark \u2013 and this is precisely the standard set by EN 301 549 and, consequently, by the BFSG and the EAA. <\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

What has changed in version 2.2<\/h3>

On 5 October 2023, the W3C published WCAG 2.2 as an official recommendation. The update is deliberately modest: it builds entirely on WCAG 2.1 and adds nine new success criteria \u2013 two at Level A, four at Level AA and three at Level AAA. Anyone who already fully complies with 2.1 is therefore not faced with a new set of rules, but rather with a manageable extension. One notable first has occurred: for the first time in the history of WCAG, a criterion has been removed, namely the technically outdated \u2018parsing\u2019 (4.1.1). All in all, WCAG 2.2 thus comprises 86 success criteria. As newer versions are backwards compatible, any page that complies with WCAG 2.2 automatically complies with 2.1 and 2.0 as well. <\/p>

An overview of the new criteria \u2013 explained in simple terms<\/h4>

The new features can be categorised according to the user groups they assist, which makes them more tangible than a simple list of numbers. The first group is aimed at people who navigate using a keyboard or who have a visual impairment: the two criteria regarding the unobscured focus position (2.4.11 and 2.4.12) require that an element controlled via the keyboard must not be hidden behind sticky headers, cookie banners or chat windows. The criterion regarding focus display (2.4.13) ensures that the focus frame is large enough and has sufficient contrast to be recognised at all. <\/p>

A second group makes life easier for people with impaired fine motor skills. The criterion on dragging (2.5.7) stipulates that anything which works via drag-and-drop must also be operable without a dragging gesture \u2013 for example, by simply tapping. The criterion on the minimum size of control elements (2.5.8) sets a lower limit for touch targets, so that buttons and links on a smartphone can be selected reliably. <\/p>

A third group reduces the cognitive load and applies to virtually every form. Consistent help (3.2.6) requires that help options, such as contact links or chat buttons, appear in the same place across all pages. The criterion on redundant input (3.3.7) prevents users from having to enter the same information multiple times during a process. And the two criteria on accessible authentication (3.3.8 and 3.3.9) ensure that login processes do not rely solely on memory or require users to solve puzzles \u2013 passkeys, magic links or pasting from a password manager must remain possible. <\/p>

What criteria a tool can check \u2013 and which it cannot<\/h4>

This is precisely where the most common fallacy lies. Some of the new criteria can be checked automatically: a button that is too small or a missing focus frame can be detected in the code. Others, however, are fundamentally beyond the scope of automated testing. Whether consistent help for the user is positioned in a truly sensible way, whether a login process can be completed without cognitive barriers, or whether a drag-and-drop alternative actually works in everyday use can only be assessed through human review and testing with assistive technologies. An automated scanner therefore provides a valuable initial guide, but does not constitute full proof of compliance. <\/p>

WCAG 2.2 and the Law \u2013 why you should implement it now<\/h4>

At present, the harmonised standard EN 301 549 still refers to WCAG 2.1 Level AA, which is why the BFSG and EAA are currently based on this version. However, the next version of the standard will adopt WCAG 2.2. Anyone who is already testing and rectifying issues against 2.2 today will not only meet the current requirements but will also avoid having to carry out a second, full audit once the new version becomes mandatory. As the update is minor and backwards-compatible, the effort involved is manageable \u2013 whilst the advantage gained is long-lasting. <\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t\t\t
\n\t\t\t\n\t\t\t\t\t\t<\/span>\n\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

\nFrom standard to certification.<\/span>\n
How to ensure robust compliance with WCAG 2.2.<\/span><\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Knowing a guideline is one thing; demonstrably complying with it is another. The path to achieving this is clearly structured and starts at a low threshold. <\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t\t
It all starts with Access Score\u00ae: our free, in-depth WCAG 2.2 scan automatically checks your website and shows you where you stand in just a few minutes. \n

Access Ready\u00ae, our in-depth audit involving real users of assistive technologies and testing via JAWS, NVDA and VoiceOver, ensures full compliance \u2013 particularly with regard to those criteria that cannot be conclusively assessed by automated means. Once all issues have been rectified, you will receive the legally reliable ifdb certificate as proof of your due diligence. \n

And to ensure that the level of security achieved is maintained after every release, Access Guard\u00ae continuously monitors your systems and flags any new barriers before they become a problem.<\/h5>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\tBook a Demo<\/span>\n\t\t\t\t\t<\/span>\n\t\t\t\t\t<\/a>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"Access\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t
\n\t\t\t\t\t
\n\t\t
\n\t\t\t\t
\n\t\t\t\t\t
FAQ<\/h6>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t

Frequently Asked Questions
about WCAG 2.2\n<\/h2>\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\tWhat is WCAG 2.2, explained simply?\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg>\t\t\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg>\t\t\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t<\/h6>\n\n\t\t\t\t\t
\n\t\t\t\t\t\t

WCAG 2.2 are the W3C\u2019s current Web Content Accessibility Guidelines \u2013 international guidelines on how to design digital content to be accessible. They form the technical basis to which legislation such as the BFSG and the EAA refer via the EN 301 549 standard. <\/p>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t\t

\n\t\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\tWhat is the difference between WCAG 2.1 and 2.2?\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg>\t\t\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg>\t\t\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t<\/h6>\n\n\t\t\t\t\t
\n\t\t\t\t\t\t

WCAG 2.2 builds entirely on version 2.1 and adds nine new success criteria, for example relating to focus visibility, control size and accessible authentication. A single criterion (parsing) has been removed. Anyone who complies with 2.2 automatically complies with 2.1 as well. <\/p>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t\t

\n\t\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\tWhat do the ratings A, AA and AAA mean?\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg>\t\t\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg>\t\t\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t<\/h6>\n\n\t\t\t\t\t
\n\t\t\t\t\t\t

A is the minimum, AA is the standard relevant to most websites and for legal compliance in Europe, and AAA is the highest level. In practice, WCAG 2.2 Level AA is the key target. <\/p>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t\t

\n\t\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\tIs WCAG 2.2 a legal requirement in Germany?\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg>\t\t\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg>\t\t\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t<\/h6>\n\n\t\t\t\t\t
\n\t\t\t\t\t\t

Indirectly. At present, the BFSG and EAA refer to WCAG 2.1 AA through EN 301 549. The next version of the standard will adopt WCAG 2.2. Anyone who adopts 2.2 now is preparing for the future. <\/p>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t\t

\n\t\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\tCan an automated tool fully validate compliance with WCAG 2.2?\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg>\t\t\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg>\t\t\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t<\/h6>\n\n\t\t\t\t\t
\n\t\t\t\t\t\t

No. Some of the criteria can be measured automatically, whilst others \u2013 such as consistent support or accessible authentication \u2013 require human assessment and testing using assistive technologies. Both are needed to provide robust evidence. <\/p>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t\t\t

\n\t\t\t\t\t\t\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\tHow do I demonstrate compliance with WCAG 2.2?\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg>\t\t\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\t\t<\/path><\/svg>\t\t\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/span>\n\t\t\t\t\t\t\t\t\t\t\t<\/h6>\n\n\t\t\t\t\t
\n\t\t\t\t\t\t

Through a documented audit and a robust certificate. The ifdb certificate from Access Ready\u00ae serves as proof of due diligence towards authorities, business partners and the courts. <\/p>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t

\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t

Meeting tomorrow\u2019s standards today.<\/h2>\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

WCAG 2.2 is not some distant dream, but the benchmark against which your digital accessibility is measured \u2013 today in practice, tomorrow by law. Let\u2019s work together to assess where your services currently stand and how you can most efficiently achieve compliance. <\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t\t\t\t\t\t\t\n\t\t\t\t\t\t\n\t\t\t\t\t\t\t\t\tBook a Demo<\/span>\n\t\t\t\t\t<\/span>\n\t\t\t\t\t<\/a>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

WCAG 2.2 in practice \u2013 understanding the web standard, demonstrating compliance<\/h4>

WCAG 2.2<\/strong> forms the technical core of any serious accessibility strategy and serves as the common point of reference for the BFSG, the EAA and EN 301 549. Anyone wishing to study the guidelines in their original form can find them as the official Web Content Accessibility Guidelines on the W3C website<\/a>, whilst the Web Accessibility Initiative\u2019s overview of the new success criteria summarises<\/a> the specific changes introduced in version 2.2. Both sources make it clear that this is not an abstract set of rules, but rather concrete, practical requirements relevant to everyday life. <\/p>

With ifdb, you can make the transition from compliance with the guidelines to demonstrated compliance: the free WCAG 2.2 scan from Access Score\u00ae<\/a> provides an initial assessment of your current status; the in-depth audit, complete with an ifdb certificate<\/a>, delivers robust evidence of compliance; and your status remains securely maintained through ongoing accessibility monitoring<\/a>. This is how a technical standard becomes a practical and demonstrable competitive advantage. <\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t","protected":false},"excerpt":{"rendered":"

DIGITAL ACCESSIBILITY \u00b7 WEB STANDARDS \u00b7 BFSG \u00b7 EAA \u00b7…<\/p>\n","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"closed","ping_status":"closed","template":"","meta":{"footnotes":""},"class_list":["post-992288","page","type-page","status-publish","hentry"],"yoast_head":"\nWCAG 2.2 explained simply: Criteria & Compliance | ifdb<\/title>\n<meta name=\"description\" content=\"WCAG 2.2 explained in simple terms: the nine new success criteria, levels A to AAA and the link to the BFSG and EAA \u2013 plus verifiable evidence from the ifdb.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/ifdb.io\/en\/wcag-2-2\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"WCAG 2.2 \u2013 the web standard behind BFSG, EAA and EN 301 549, explained\" \/>\n<meta property=\"og:description\" content=\"The nine new success criteria, levels A to AAA and the legal context \u2013 succinctly explained. Plus: How to provide robust evidence of compliance.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/ifdb.io\/en\/wcag-2-2\/\" \/>\n<meta property=\"og:site_name\" content=\"ifdb \u2013 digitale Barrierefreiheit & BFSG-Konformit\u00e4t\" \/>\n<meta property=\"article:modified_time\" content=\"2026-10-12T09:36:35+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/ifdb.io\/wp-content\/uploads\/2026\/05\/IFDB_AccessDoc_Dashboard-Homescreen-1024x728.png\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:title\" content=\"WCAG 2.2: nine new criteria, one standard\" \/>\n<meta name=\"twitter:description\" content=\"From focus visibility to accessible login \u2013 what\u2019s new in WCAG 2.2 and why you should start implementing it today.\" \/>\n<meta name=\"twitter:label1\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data1\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/ifdb.io\\\/en\\\/wcag-2-2\\\/\",\"url\":\"https:\\\/\\\/ifdb.io\\\/en\\\/wcag-2-2\\\/\",\"name\":\"WCAG 2.2 explained simply: Criteria & Compliance | ifdb\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/ifdb.io\\\/en\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/ifdb.io\\\/en\\\/wcag-2-2\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/ifdb.io\\\/en\\\/wcag-2-2\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/ifdb.io\\\/wp-content\\\/uploads\\\/2026\\\/05\\\/zdf-logo.png\",\"datePublished\":\"2026-05-25T15:24:35+00:00\",\"dateModified\":\"2026-10-12T09:36:35+00:00\",\"description\":\"WCAG 2.2 explained in simple terms: the nine new success criteria, levels A to AAA and the link to the BFSG and EAA \u2013 plus verifiable evidence from the ifdb.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/ifdb.io\\\/en\\\/wcag-2-2\\\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/ifdb.io\\\/en\\\/wcag-2-2\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/ifdb.io\\\/en\\\/wcag-2-2\\\/#primaryimage\",\"url\":\"https:\\\/\\\/ifdb.io\\\/wp-content\\\/uploads\\\/2026\\\/05\\\/zdf-logo.png\",\"contentUrl\":\"https:\\\/\\\/ifdb.io\\\/wp-content\\\/uploads\\\/2026\\\/05\\\/zdf-logo.png\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/ifdb.io\\\/en\\\/wcag-2-2\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\\\/\\\/ifdb.io\\\/en\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"WCAG 2.2\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/ifdb.io\\\/en\\\/#website\",\"url\":\"https:\\\/\\\/ifdb.io\\\/en\\\/\",\"name\":\"ifdb\",\"description\":\"Audit, Zertifizierung und Haftungsschutz f\u00fcr digitale Barrierefreiheit\",\"publisher\":{\"@id\":\"https:\\\/\\\/ifdb.io\\\/en\\\/#organization\"},\"alternateName\":\"ifdb GmbH\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/ifdb.io\\\/en\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/ifdb.io\\\/en\\\/#organization\",\"name\":\"ifdb GmbH\",\"alternateName\":\"ifdb\",\"url\":\"https:\\\/\\\/ifdb.io\\\/en\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\\\/\\\/ifdb.io\\\/en\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/ifdb.io\\\/wp-content\\\/uploads\\\/2026\\\/06\\\/ifdb_logo.png\",\"contentUrl\":\"https:\\\/\\\/ifdb.io\\\/wp-content\\\/uploads\\\/2026\\\/06\\\/ifdb_logo.png\",\"width\":1366,\"height\":590,\"caption\":\"ifdb GmbH\"},\"image\":{\"@id\":\"https:\\\/\\\/ifdb.io\\\/en\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.instagram.com\\\/ifdb.io\\\/\",\"https:\\\/\\\/www.linkedin.com\\\/company\\\/ifdb-io\\\/\"]}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"WCAG 2.2 explained simply: Criteria & Compliance | ifdb","description":"WCAG 2.2 explained in simple terms: the nine new success criteria, levels A to AAA and the link to the BFSG and EAA \u2013 plus verifiable evidence from the ifdb.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/ifdb.io\/en\/wcag-2-2\/","og_locale":"en_US","og_type":"article","og_title":"WCAG 2.2 \u2013 the web standard behind BFSG, EAA and EN 301 549, explained","og_description":"The nine new success criteria, levels A to AAA and the legal context \u2013 succinctly explained. Plus: How to provide robust evidence of compliance.","og_url":"https:\/\/ifdb.io\/en\/wcag-2-2\/","og_site_name":"ifdb \u2013 digitale Barrierefreiheit & BFSG-Konformit\u00e4t","article_modified_time":"2026-10-12T09:36:35+00:00","og_image":[{"url":"https:\/\/ifdb.io\/wp-content\/uploads\/2026\/05\/IFDB_AccessDoc_Dashboard-Homescreen-1024x728.png","type":"","width":"","height":""}],"twitter_card":"summary_large_image","twitter_title":"WCAG 2.2: nine new criteria, one standard","twitter_description":"From focus visibility to accessible login \u2013 what\u2019s new in WCAG 2.2 and why you should start implementing it today.","twitter_misc":{"Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/ifdb.io\/en\/wcag-2-2\/","url":"https:\/\/ifdb.io\/en\/wcag-2-2\/","name":"WCAG 2.2 explained simply: Criteria & Compliance | ifdb","isPartOf":{"@id":"https:\/\/ifdb.io\/en\/#website"},"primaryImageOfPage":{"@id":"https:\/\/ifdb.io\/en\/wcag-2-2\/#primaryimage"},"image":{"@id":"https:\/\/ifdb.io\/en\/wcag-2-2\/#primaryimage"},"thumbnailUrl":"https:\/\/ifdb.io\/wp-content\/uploads\/2026\/05\/zdf-logo.png","datePublished":"2026-05-25T15:24:35+00:00","dateModified":"2026-10-12T09:36:35+00:00","description":"WCAG 2.2 explained in simple terms: the nine new success criteria, levels A to AAA and the link to the BFSG and EAA \u2013 plus verifiable evidence from the ifdb.","breadcrumb":{"@id":"https:\/\/ifdb.io\/en\/wcag-2-2\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/ifdb.io\/en\/wcag-2-2\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/ifdb.io\/en\/wcag-2-2\/#primaryimage","url":"https:\/\/ifdb.io\/wp-content\/uploads\/2026\/05\/zdf-logo.png","contentUrl":"https:\/\/ifdb.io\/wp-content\/uploads\/2026\/05\/zdf-logo.png"},{"@type":"BreadcrumbList","@id":"https:\/\/ifdb.io\/en\/wcag-2-2\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/ifdb.io\/en\/"},{"@type":"ListItem","position":2,"name":"WCAG 2.2"}]},{"@type":"WebSite","@id":"https:\/\/ifdb.io\/en\/#website","url":"https:\/\/ifdb.io\/en\/","name":"ifdb","description":"Audit, Zertifizierung und Haftungsschutz f\u00fcr digitale Barrierefreiheit","publisher":{"@id":"https:\/\/ifdb.io\/en\/#organization"},"alternateName":"ifdb GmbH","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/ifdb.io\/en\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/ifdb.io\/en\/#organization","name":"ifdb GmbH","alternateName":"ifdb","url":"https:\/\/ifdb.io\/en\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/ifdb.io\/en\/#\/schema\/logo\/image\/","url":"https:\/\/ifdb.io\/wp-content\/uploads\/2026\/06\/ifdb_logo.png","contentUrl":"https:\/\/ifdb.io\/wp-content\/uploads\/2026\/06\/ifdb_logo.png","width":1366,"height":590,"caption":"ifdb GmbH"},"image":{"@id":"https:\/\/ifdb.io\/en\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.instagram.com\/ifdb.io\/","https:\/\/www.linkedin.com\/company\/ifdb-io\/"]}]}},"_links":{"self":[{"href":"https:\/\/ifdb.io\/en\/wp-json\/wp\/v2\/pages\/992288","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ifdb.io\/en\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/ifdb.io\/en\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/ifdb.io\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/ifdb.io\/en\/wp-json\/wp\/v2\/comments?post=992288"}],"version-history":[{"count":2,"href":"https:\/\/ifdb.io\/en\/wp-json\/wp\/v2\/pages\/992288\/revisions"}],"predecessor-version":[{"id":992785,"href":"https:\/\/ifdb.io\/en\/wp-json\/wp\/v2\/pages\/992288\/revisions\/992785"}],"wp:attachment":[{"href":"https:\/\/ifdb.io\/en\/wp-json\/wp\/v2\/media?parent=992288"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}