In early 2020, the Accessibility Guidelines Working Group (AG WG) announced the First Public working draft of the Web Content Accessibility Guidelines (WCAG) 2.2. This working draft covers the potential success criteria that were considered during the development of WCAG 2.1 but were not published in the 2.1 guidelines due to the need for more time to develop the criteria and because it required other specifications to mature before being introduced.
Comparison between the previous WCAG versions
WCAG 2.1 AA has 50 (38 + 12 new success criteria)
WCAG 2.2 AA will have 59 (50 + 9 new success criteria)
New features in WCAG 2.2
The latest working draft of WCAG 2.2 was released in August 2020 and outlines nine new success criteria and one updated current success criteria. The following are the new Success Criteria defined in WCAG 2.2.
- 3.3.7 (Level A) Accessible Authentication
- 2.5.7 (Level AA) Dragging
- 3.2.6 (Level A) Findable Help
- 2.4.13 (Level A) Fixed Reference Points
- 2.4.11 (Level AA) Focus Appearance (Minimum)
- 2.4.12 (Level AAA) Focus Appearance (Enhanced)
- 3.2.7 (Level AA) Hidden Controls
- 2.5.8 (Level AA) Pointer Target Spacing
- 3.3.8 (Level A) Redundant Entry
To avoid confusion in the numbering and reference, these new success criteria have been appended to the end of the success criteria in previous guidelines rather than in between existing criteria. This removes the need to change section numbers to accommodate them. However, this new numbering system also means that the success criteria in each guideline are no longer grouped by conformance level. Website authors can refer to the conformance level (A, AA, and AAA) via the conformance level indicator listed on each success criterion.
When will it be published?
How will this affect my current compliance?
WCAG 2.2 is built upon the work started in WCAG 2.1 that was inherited from WCAG 2.0. The guidelines are focused on accessibility for users with cognitive or learning disabilities, users with low vision, and users with disabilities on mobile devices. The WCAG 2.2 is thus backward compatible with WCAG 2.1 and 2.0. It is also expected that any accessibility legislation that references WCAG 2.0 or 2.1 will eventually refer to 2.2. So websites that are required to conform with either WCAG 2.1 or 2.0 will be able to update their content to WCAG 2.2 standards without affecting their conformance.
Checklist: How to meet the new WCAG 2.2 success criteria
If an authentication process relies on a cognitive function test, that requires the user to remember, manipulate, or transcribe information (think CAPTCHA, math equations, or answering logic puzzles), you should provide an alternative to the authentication method that does not utilize cognitive function tests, like two-factor authentication.
2.5.7 (Level AA) Dragging
Any functionality that requires a dragging movement by a pointer (cursor, finger on a touch screen, etc.), such as adjusting a slider button, a carousel, etc., should be operable in other ways like clicking unless the dragging action is absolutely essential to the functionality of the content.
3.2.6 (Level A) Findable Help
Help options such as a Contact Us page, chatbots, FAQs, messaging applications, help centers, or other support options, should be findable and be in a consistent location on every page.
2.4.13 (Level A) Fixed Reference Points
If you have an electronic publication on your website with pagebreak locators (page numbering), make sure that there is a mechanism in place to navigate between each page and that the numbering maintains its place even when the platform where the publication is hosted changes or it is printed.
2.4.11 (Level AA) Focus Appearance (Minimum)
Ensure that the keyboard focus indicators of user interface component (menus, links, forms, etc.) have a clear border, are not obscured by other content, and have a color contrast ratio of at least 3:1 against the unfocused state and all adjacent colors.
2.4.12 (Level AAA) Focus Appearance (Enhanced)
Similar to the Criterion 2.4.11, ensure that the keyboard focus indicators of user interface components have a clear border, are not obscured by other content, and have a color contrast ratio of at least 4:5:1 against the unfocused state and all adjacent colors.
3.2.7 (Level AA) Hidden Controls
Controls, such as buttons, that are vital to a process need to be visible and accessible when needed and not require an action like a pointer hover or keyboard focus to make them/keep them visible.
2.5.8 (Level AA) Pointer Target Spacing
Every target, such as links, must have a hit-area of at least 44x44 CSS pixels to make it easier for users to select it with a pointer (clicking with a cursor, selecting with a touch-screen, etc.).
3.3.8 (Level A) Redundant Entry
When completing a process like filling in a form online, the information that was previously entered by the user must be auto-filled or available as a selection, unless the process involves a security verification.