_
Lets work together
_
Introduction to WCAG 2.2: New Guidelines for Web Accessibility
As digital services evolve, so do the accessibility requirements. With the updated recommendations for web accessibility, higher demands are placed on companies. Small adjustments, such as larger buttons and simpler navigation, can make a world of difference for your users. Read on to get insight into the most important changes.
_
What Is WCAG?
WCAG stands for Web Content Accessibility Guidelines, a set of recommendations for web accessibility developed by the World Wide Web Consortium (W3C). It's the most widely used reference in web accessibility legislation, and W3C regularly adds new criteria as new needs emerge.
Soon, even greater focus will be placed on building accessible, user-friendly websites that meet everyone's needs, regardless of disability.
WCAG 2.2 has already been published, but the European standard EN 301 549 hasn't yet been updated to reference it — EN 301 549 still builds on WCAG 2.1. An updated version is in the works and expected during 2026, so it's worth starting the planning now.
Here's an overview of the new success criteria in WCAG 2.2. They aren't yet a legal requirement in the EU, but are in development and expected during 2026. It's a good idea to know and follow them already.
2.4.11 Focus Not Obscured
This success criterion requires that a focused element isn't completely hidden behind other content on the page — for example cookie banners or pop-up messages. This means users navigating by keyboard can always see where their focus is.
2.5.7 Dragging Movements
This success criterion requires that functions normally performed by dragging — for example with a mouse or a finger on a touchscreen — can also be performed without dragging, such as with a single click or tap. This helps users who struggle with precise or sustained dragging movements, whether they use a mouse, touchscreen, or other pointing device. One example is a video player, where you'd normally scrub by dragging the playhead — here it should also be possible to jump to a specific point with a single click.
2.5.8 Target Size
This success criterion sets requirements for the size of interactive elements such as buttons and links: as a rule, they should be at least 24×24 CSS pixels, or have sufficient spacing from other clickable elements if the target itself is smaller. This helps users with motor impairments and generally makes it easier to tap the right spot on small screens.
_
Web Accessibility: A Complete Overview
For many private businesses, web accessibility is still uncharted territory, so we've gathered the key knowledge in one place to help you get started with the necessary changes and meet the EAA requirements that took effect in June 2025.
Browse our whitepaper for the full picture, and to get an idea of some of the key accessibility requirements — as well as what your business stands to gain from implementing web accessibility.
(hint: it pays off!)
Download The Whitepaper
_
Who Must Comply with the New WCAG 2.2 Guidelines?
Public sector organisations have been required to meet WCAG 2.1 accessibility requirements since 2016. While WCAG 2.2 isn't yet a formal legal requirement, it's a good idea to start adapting digital solutions to the new criteria now, so you're ready once EN 301 549 is updated.
Since June 2025, the requirements have also applied to a wide range of private businesses through the European Accessibility Act (EAA).
_
Leave It to the Professionals
Since 2016, Kruso has helped a wide range of public sector organisations ensure web accessibility across their platforms, and we're ready to give your platform a thorough check.
Get in touch for a helping hand in making your digital solutions fit for the accessibility requirements of the future!