Web Content Accessibility Guidelines (WCAG) have changed again. Although the European Accessibility Act (which will come into effect in June 2025) requires only the WCAG 2.1 AA standards, knowing and applying the new guidelines is crucial if you want to target a large audience, especially in a field such as finance. What did the update change? Find it out in this article!

Table of Contents

The Main Changes in Web Content Accessibility Guidelines 2.2

So, what’s new in the WCAG 2.2? The new version of the guidelines removes one of the points (4.1.1 Parsing) and adds 9 new points that you need to consider when building your website or apps. Let’s look at them in more detail.

Removed: 4.1.1 Parsing

4.1.1 Parsing was introduced when old technology was in place, and the sites handled parsing errors on their own. However, with modern HTML or XML, this is done on the browser side, so this criterion is always completed, hence becoming obsolete and removed in the WCAG 2.2.

Added: 2.4.11 Focus Not Obscured (Minimum) (AA)

The 2.4.11 Focus Not Obscured point determines that you must ensure that an item focused on the keyboard is at least partially visible. This part of the UX design is dedicated to those users who cannot navigate the site or app using a mouse.

Added: 2.4.12 Focus Not Obscured (Enhanced) (AAA)

Point 2.4.12 takes Focus Not Obscured to the next level. To meet this guideline, you need to ensure that when an element gets keyboard focus, it is fully visible to the user.

Added: 2.4.13 Focus Appearance (AAA)

The third point added in the WCAG 2.2 refers to the size of the focus indicator. According to the new guidelines, it should be at least as large as the area of a 2 CSS pixel thick perimeter around the component, as well as have at least a 3:1 contrast ratio between the same pixels in the unfocused and focused areas.

Added: 2.5.7 Dragging Movements (AA)

This point states that any action involving movement, like dragging, should be achievable with a single pointer since some users cannot perform dragging motions. There is an exception to this: actions where dragging is essential, or the user agent determines the functionality.

Added: 2.5.8 Target Size (Minimum) (AA)

This specific point in the Web Content Accessibility Guidelines defines the size of pointer targets. According to the document, the size should be at least 24×24 CSS pixels unless:

  • it is possible to create a 24×24 circle around an undersized target that will not intersect with other targets,
  • the function can be achieved through different controls,
  • the target is a sentence, or the line height constrains its size,
  • the user agent determines the size,
  • the specific presentation is required legally or essential to conveying the information as intended.

Added: 3.2.6 Consistent Help (A)

This point is strongly related to the best practices for customer experience in banking. It states that the same help mechanism should be used across all subpages in the same place on each page. This refers to the following mechanism:

  • human contact details,
  • human contact mechanisms,
  • self-help options (e.g., FAQs),
  • fully automated contact mechanisms (e.g., banking chatbots).

Added: 3.3.7 Redundant Entry (A)

This WCAG 2.2 point states that information that the user is required to re-enter should either be:

  • re-entered automatically,
  • available for the user to select from a list.

There are 3 exceptions to this guideline; it is not required when:

  • the entered information is essential,
  • the entered information is required to ensure the security of the content,
  • the entered information is no longer valid.

Added: 3.3.8 Accessible Authentication (Minimum) (AA)

This new guideline states that a cognitive function test (e.g., remembering a password or solving a puzzle) should not be required for any step in an authentication process. However, it points out several exceptions:

  • when an alternative authentication method that does not rely on a cognitive test is available,
  • there is a mechanism that helps the user complete the cognitive test,
  • the cognitive function test requires the user to recognize objects,
  • the test is used to identify non-text content provided by the user to the website.

Added: 3.3.9 Accessible Authentication (Enhanced) (AAA)

This particular point is almost the same as the previous one but includes fewer exceptions. According to it, there should not be a cognitive function test unless:

  • when an alternative authentication method that does not rely on a cognitive test is available,
  • there is a mechanism that helps the user complete the cognitive test.

The Takeaway

Achieving high-level accessibility is crucial, not only to comply with the European Accessibility Act but also to attract more users and deliver better customer experiences. Therefore, if you do not meet any of the above mentioned guidelines, we suggest that you change that as soon as possible. What if you don’t know how to do it? Contact us at Ailleron – we will help you adjust your website or banking app.

You may also read: AI Act – What Is It? Who Does It Affect? What Will It Change?

Ailleron - Web Content Accessibility Guidelines (WCAG) 2.2

Ailleron

Ailleron Marketing team includes digital marketers and content creators who provide insights and expertise from across the organization, including #AilleronExperts. For media queries, please get in touch with us via our contact form.

Share on social media

Applying graph neural networks for hyper-personalized banking services

Read more
Show all insights

You may be also interested in:

Show all insights
abstract lines

Let’s make financial experiences
easy and enjoyable together!

Tell us what you need and we will contact you shortly.

Tell us what you need and we will contact you shortly.