WCAG 2.2: What is it and why must your website comply?

What is WCAG?

WCAG (Web Content Accessibility Guidelines) is an international standard developed by the W3C that defines how to make web content accessible to people with disabilities – including users with visual, auditory, motor, and cognitive impairments.

In 2026, the current version is WCAG 2.2, which was published in October 2023 (W3C official).

Three levels of compliance

• A – minimum (mandatory baseline)
• AA – standard (EU requirement for the public sector and many private companies)
• AAA – highest (for specific conditions)

EU directive European Accessibility Act (EAA) came into force on 28 June 2025 and requires AA-level compliance from many private companies: e-shops, banks, transport services, e-books, and mobile applications.

What changed in WCAG 2.2?

9 new success criteria were added, including:

• 2.4.11 Focus Not Obscured – the focus indicator must be visible, not hidden under a cookie banner or chat widget
• 2.5.7 Dragging Movements – all dragging actions must be replaceable with a single click
• 2.5.8 Target Size (Minimum) – clickable elements must be at least 24×24 pixels
• 3.3.7 Redundant Entry – do not request the same information twice within the same process
• 3.3.8 Accessible Authentication – do not require memory or cognitive tests for logging in (e.g., CAPTCHAs that require identifying images)

Who does this affect in Estonia?

1. Public sector – mandatory since 2018 (Information System Authority)
2. E-shops and service providers – mandatory under the EAA since 28.06.2025
3. B2B companies – you risk losing tenders if the bids require WCAG AA compliance
4. Everyone – Google rewards accessible pages with better rankings

What happens if you don't comply?

• Fines of up to €20,000 (in Estonia, monitored by the CPRA)
• Civil lawsuits (a growing trend in the EU)
• Reputational damage and lost customers
• SEO impact – Google indexes accessible content more effectively

How to get started?

1. Audit – use WAVE or axe DevTools
2. Fix critical issues – contrast ratios, alt-texts, keyboard navigation
3. Test with real users – do not rely solely on automated tools
4. Add an accessibility statement – mandatory for the public sector

We can help with WCAG 2.2 AA auditing and compliance – see website maintenance and web security. Also read our GDPR guide and 10 steps to website security.

Summary

WCAG 2.2 AA is no longer just a "nice to have" – it is a legal requirement for many Estonian companies. The earlier you start, the lower the cost and risk.