Accessibility · May 28, 2026

WCAG 2.2 explained simply: the key criteria

WCAG 2.2 is the benchmark for accessible websites – but as a standard, it initially feels abstract. We translate the most important criteria into plain language and show what they mean for your site in concrete terms.

WCAG stands for “Web Content Accessibility Guidelines” – the internationally recognized guidelines for accessible web content. Version 2.2 is the current state and forms the basis for most legal requirements. Those who understand them build better websites: more accessible, clearer, and often easier to find.

This article explains the four core principles and the most important criteria in everyday language. We offer auditing and implementation according to these criteria as part of our Accessibility service.

The four principles of the WCAG

All criteria fall under four principles. A website should be:

  • Perceivable: Content must be accessible to all senses – for example, via alternative text or sufficient contrast.
  • Operable: Everything must be usable without a mouse, with a clearly visible focus.
  • Understandable: Language, structure, and operation must be easy to follow.
  • Robust: Content must work reliably with different devices and assistive technologies.

The most important success criteria in everyday practice

In practice, it always comes down to the same points:

  • Contrast: Text must stand out clearly from the background (at least 4.5:1 for normal text).
  • Keyboard operation: Every function is reachable via Tab – with visible focus.
  • Alternative texts: Images carrying information need a meaningful description.
  • Labeled forms: Every field has a clear label, errors are easy to understand.
  • Logical structure: Headings and order make sense even without the layout.
  • Understandable links: Link texts say where they lead – no “click here”.

What’s new in 2.2

Version 2.2 primarily adds criteria that improve mobile use and operability: more easily reachable controls, visible focus, simpler authentication without memory tests, and consistent help options. So it is less about major overhauls and more about well-thought-out details that make the difference in everyday use.

Conformance levels: A, AA, AAA

The WCAG define three levels. A is the minimum, AAA the maximum. In practice – and as the basis of the common regulations – level AA is the target: a realistic, effective standard that removes most barriers without sacrificing creative freedom.

From the standard to a usable website

Ticking off criteria isn't enough – what matters is real usability. That's why we test automatically and verify manually with keyboard and screen reader. To learn how a complete audit works, read our article Accessibility Check & WCAG Audit. Clean implementation pays off twice: an accessible site is usually also faster and easier for search engines to read – we implement it directly in the code.

What the implementation costs

The effort depends on the starting point: if accessibility was considered from the beginning, targeted corrections are often enough; older sites may need more. We prioritize by impact so the biggest barriers fall first. In a first, no-obligation conversation, we give an initial assessment after a quick look at your site.

Frequently asked questions

What does WCAG 2.2 mean in simple terms?

They are the internationally recognized guidelines ensuring web content is usable for everyone – organized around the principles perceivable, operable, understandable, and robust. Version 2.2 is the current standard.

Which conformance level should we aim for?

In practice, level AA is the target. It removes most of the relevant barriers and is the basis of the common standards, without excessively restricting the design.

What is new in WCAG 2.2 compared to 2.1?

2.2 primarily adds criteria around mobile usability, visible focus, simpler authentication, and consistent help. These are mostly well-considered details rather than major overhauls.

Is it enough to check the criteria automatically?

No. Automated testing covers part of it; real usability only shows in manual checks with keyboard and screen reader. We combine both.

Does accessibility also improve Google rankings?

Indirectly, yes: clean structure, good contrast, meaningful alt texts, and fast load times help both people and search engines. Accessibility and SEO go hand in hand.

What does implementation according to WCAG 2.2 cost?

That depends on the starting point. If accessibility was considered from the beginning, targeted corrections suffice; with legacy content, more may be needed. We prioritize by impact and give an assessment in an initial consultation.

Build your website to WCAG 2.2?

We audit your site against WCAG 2.2 and implement the most important improvements directly in the code – clearly documented and prioritized by impact.

Request a project

More insights