Copenhagen
Landemærket 10, 6th floor1119 Copenhagen
Denmark+45 33 36 44 44hello@kruso.dk
Introduction to WCAG 2.2: New Guidelines for Web Accessibility
As digital services evolve, so do the accessibility requirements. Is your web solution ready?
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. But what do the new rules mean for you? Read on to get insights into the most important changes.Â
What is WCAG?
WCAG stands for Web Content Accessibility Guidelines, and it is a set of recommendations for web accessibility developed by the World Wide Web Consortium (W3C). These are the most commonly used guidelines in web accessibility legislation, and W3C regularly releases new updates as new needs arise.Â
 Â
Soon, there will be an even greater focus on creating accessible, user-friendly websites that meet everyone’s needs, regardless of disabilities. WCAG 2.2 has already been released, and in 2025, the European standard EN 301 549 is expected to be updated with the latest recommendations. For both private and public companies operating within the EU, it is important to stay informed about these changes. Currently, EN 301 549 is based on WCAG 2.1 recommendations, but an updated version is expected to be fully implemented by 2025, so it makes sense to start planning now.Â
Here is an overview of the new WCAG 2.2 rules expected to be implemented into legislation in 2025:
2.4.11 Focus Not Obscured
This guideline requires that a user's focus element must not be obscured by other content on the page, such as cookie banners and pop-up messages. This ensures that users navigating with a keyboard can always see where their focus is.Â
2.5.7 Dragging Movements
To enhance user experience, dragging movements on touch screens must be replaceable with simpler alternatives. This helps users who find it difficult to perform complex finger movements on mobile devices. For example, in videos where you can drag the scrubber back and forth, it must also be possible to fast forward to a specific point simply by clicking with the mouse.Â
2.5.8 Target Size
This guideline sets a requirement for the size of interactive elements such as buttons and links. They must be at least 24x24 pixels, helping users with motor impairments or those navigating with large fingers on small screens.Â
3.2.6 Consistent Help
When help options, such as chat functions or FAQs, are available on a website, they must be consistent across the entire site. This ensures that users can always find assistance no matter where they are on the page.Â
3.3.7 Redundant Entry
Users should avoid having to repeat the same information multiple times. For example, if a user has already entered their address in the delivery field, the system should store this information so that it doesn’t have to be re-entered in the billing address field.Â
3.3.8 Accessible Authentication
When it comes to authentication (e.g., login), users with cognitive or motor impairments should be able to use solutions without having to remember passwords or perform complex actions. Alternatives such as biometric login or passwords sent via email or SMS are recommended.Â
Who must comply with the new WCAG 2.2 guidelines?
Public organizations have been required to comply with WCAG 2.1 accessibility standards since 2016, and they must now begin updating their digital solutions in line with version 2.2.Â
 Â
From 2025, these requirements will also apply to a wide range of private companies under the European Accessibility Act (EAA). This law will cover e-commerce companies, banks, transport providers, media platforms, and other service providers that rely on digital platforms. For these companies, it is crucial to begin adapting their digital solutions now to avoid potential sanctions and improve accessibility for all users. For many private companies, web accessibility is unfamiliar territory, and it can take a long time to implement correctly.Â