new WCAG 2.2

Learn about the changes to the new WCAG 2.2 and an update on its status

The release of WCAG 2.2 is expected by the end of 2022, giving  way to the new version of the Web Content Accessibility Guidelines (WCAG).

These changes, which constitute a minor update of the last version of the WCAG, will still be compatible with WCAG 2.0 and WCAG 2.1 which are still eminently valid and useful.

The main difference in WCAG 2.2 is that nine new requirements have been added to WCAG 2.0 and WCAG 2.1; the new guidelines will still employ the same conformance levels, namely A/AA/AAA.

It is important to note that the new requirements that have been proposed in version 2.2 may still undergo changes, as they are currently under review and may be subject to further changes.

Which makes this the perfect time for us to learn about how the new criteria will impact accessible web design and development and digital content.

That is why we’re here to tell you about the main changes to be included in WCAG 2.2.; take note of this new development, which will bring about an even greater level of web accessibility than ever before.

New Success Criteria proposed for WCAG 2.2

As mentioned above, the proposal includes nine new points which are still open to review, comments and changes. This means that there is no guarantee that all of them be included in the Final Recommendation.

The list of new Success Criteria, as per the September 2022 version of the guidelines (in the form of a Candidate Recommendation), are:

2.4.11 Focus Appearance (Level AA)

This Success Criterion will allow sighted people who navigate using a keyboard to visually locate the point of focus of their keyboard.

Here, the requirement stipulates that the “focus indicator” showing the focus point of the keyboard be visible at all times.

2.4.12 Focus Not Obscured (Minimum) (Level AA)

The aim of this Success Criterion is to ensure that the “focus indicator” is not hidden behind overlapping content.

This refers to situations where content may cover the page having current keyboard focus. Problematic content includes elements such as cookie pop-ups, sticky headers, etc.

2.4.13 Focus Not Obscured (Enhanced) (Level AAA)

The only difference with respect to the previous Success Criterion is that at Conformance Level AAA, the entire focus indicator must be visible. It thereby meets the same objective, but is stricter than before.

2.5.7 Dragging Movements (Level AA)

We all know that dragging and releasing require fairly precise movements in which users must keep their finger on the button on the screen without releasing it.

This action can be quite difficult for people with motor impairment. The aim of this criterion is to ensure that dragging and dropping can be performed using methods other than those we are familiar with.

2.5.8 Target Size (Minimum) (Level AA)

In this guideline, a minimum distance between the interaction elements is proposed so that people who are unable to execute fine movements with their hands can click on smaller buttons more easily, reducing the risk of errors.

3.2.6 Consistent help (Level A)

In order for users to easily find the help they need, this criterion establishes that the help functions found on multiple web pages within a website should appear in the same place.

This will help people with cognitive impairment who need to follow a particular pattern of steps to complete a task.

3.3.7 Accessible Authentication (Level AA)

Authentication without the need for a cognitive function test is the goal of this criterion. This will help people with motor disabilities or cognitive impairment such as dyslexia or memory problems, for example.

How will it achieve this? By requiring the inclusion of authentication functions that are easier and more direct.

Like, for example, allowing users to reset their password using their email address without needing to transcribe codes sent to their mobile phones.

3.3.8 Accessible Authentication (No Exception) (Level AAA)

While this criterion also aims to make authentication much more accessibleas in the one above it is also more strict.

This means that cognitive function tests will only be allowed if they use an alternative authentication method that does not involve the recognition of non-textual personal content.

3.3.9 Redundant Entry (Level A)

In order to avoid re-entry of redundant data by users,this criterion seeks to minimize difficulties for people with motor or cognitive disabilities eliminating the need to enter the same information a second time.

In this way, WCAG 2.2 seeks to better cover the needs of people with disabilities, ensuring web accessibility that will enable them to navigate the Web freely and independently.

Here at inSuit, we are fully aligned with all the updates and news related to the Web Content Accessibility Guidelines (WCAG).

Our aim is to provide you with web accessibility services that fully conform to national and international regulations. So, if you are looking to make your page accessible, contact usthere is no obligation to purchase.