WCAG 2.2 current status

The WCAG 2.2 release got pushed again. This time they are planning for a Q3 release. There has been a couple of changes since the last time I wrote about this topic. If you haven't been following the criteria, it might be useful for you to check my previous blog post on this topic. I won't list all the criteria here, only the changes that have been added since my previous post.

They decided to go back on one of the WCAG 2.1 changes. 2.4.7 Focus Visible was changed back to level AA so this criterion will remain as it is in WCAG 2.1. The only change to WCAG 2.1 will be the removal of 4.1.1 Parsing.

Changes to the new criteria for 2.2

They changed the numbering for 2.4.11, 2.4.12, and 2.4.13. And the same was done for 3.3.7, 3.3.8, and 3.3.9. In both these cases, the AAA-level criteria are now the last on the list. This is how the criteria have been also in the earlier versions.

Criteria 2.5.7 Dragging Movements and 3.2.6 Consistent Help remain as they have been.

2.4.11 and 2.4.12 Focus obscured - minimum and enhanced

2.4.11 is now Focus Not Obscured (Minimum), which is the AA level criterion. And 2.4.12 is Focus Not Obscured (Enhanced), which is the AAA level criterion. The criteria themselves are still the same as they were before.

2.4.13 Focus appearance

2.4.13 Focus Appearance is the criterion that was earlier at risk. The criteria will be kept, but it will be an AAA-level criterion. They've also changed the criterion description quite a bit.

When the keyboard focus indicator is visible, an area of the focus indicator meets all the following:

• is at least as large as the area of a 2 CSS pixel thick perimeter of the unfocused component or sub-component, and
• has a contrast ratio of at least 3:1 between the same pixels in the focused and unfocused states

Exceptions:

• The focus indicator is determined by the user agent and cannot be adjusted by the author, or
• The focus indicator and the indicator's background color are not modified by the author.

There are also three notes attached, which should provide some more context. The criterion is now much more understandable to me. I kind of feel bad for not getting more requirements for the focus indicator on A or AA level. But at least we now get more requirements for the AAA level. And I will be recommending all my clients to meet this criterion regardless of what they must follow. The clearer and better visibility we can have in the focus styles of an element, the easier it is to perceive.

2.5.8 Target size (Minimum)

They changed the exceptions for spacing and inline. The criterion is now as follows:

The size of the target for pointer inputs is at least 24 by 24 CSS pixels, except where:

• Spacing: Undersized targets (those less than 24 by 24 CSS pixels) are positioned so that if a 24 CSS pixel diameter circle is centered on the bounding box of each, the circles do not intersect another target or the circle for another undersized target;
• Equivalent: The function can be achieved through a different control on the same page that meets this criterion;
• Inline: The target is in a sentence or its size is otherwise constrained by the line-height of non-target text;
• User agent control: The size of the target is determined by the user agent and is not modified by the author;
• Essential: A particular presentation of the target is essential or is legally required for the information being conveyed.

So they've added a bit more information for those two exceptions. Good changes! The clearer the criteria are, the easier they are to follow and test.

3.3.7 Redundant Entry

This criterion was 3.3.9 before. The criterion wasn't changed, just the number.

3.3.8 Accessible Authentication (Minimum)

This criterion was 3.3.7 in the previous version. They also added the word minimum to the criterion name. The content of the criterion remains the same.

3.3.9 Accessible Authentication (Enhanced)

This criterion was 3.3.8 in the previous version. The content of the criterion remains the same.