New in WCAG 2.2
Important!
The following is NOT the Web Content Accessibility Guidelines (WCAG) 2. It is a checklist that presents our recommendations for implementing the most common accessibility principles and techniques for those seeking WCAG conformance. The language used here significantly simplifies and condenses the official WCAG 2.2 specification and supporting materials to make it easier to implement and verify for web pages. The first column of the table below links to the official success criteria.
A PDF version of this checklist is also available
Operable
Guideline 2.4
Provide ways to help users navigate, find content, and determine where they are.
2.4.11 Focus Not Obscured (Minimum)
AA 2.2
- When elements have keyboard focus, they are not entirely covered or hidden by page content.
2.4.12 Focus Not Obscured (Enhanced)
AAA 2.2
- When elements have keyboard focus, they are entirely visible.
2.4.13 Focus Appearance
AAA 2.2
- If a custom focus indicator or background color is in place, the focus indicator pixels must:
- have at least 3:1 contrast between focused/unfocused states
- be at least as large as the area of a 2 pixel thick perimeter surrounding the element. The formula
(width × 4) + (height × 4) = focus indicator areacan be used for rectangular components.
Guideline 2.5
Make it easier for users to operate functionality through various inputs beyond keyboard.
2.5.7 Dragging Movements
AA 2.2
- Functionality that uses pointer dragging can also be achieved using a single pointer without dragging (unless dragging is essential).
2.5.8 Target Size (Minimum)
AA 2.2
- Pointer input target sizes are at least 24 by 24 pixels unless:
- A 24 pixel diameter circle centered on the target element does not intersect with any other target or a 24 pixel circle centered on an adjacent target.
- The functionality can be achieved in some other conformant manner.
- The target is in a sentence or list.
- The target size can't be modified or is essential to the functionality.
Understandable
Guideline 3.2
Make Web pages appear and operate in predictable ways.
3.2.6 Consistent Help
A 2.2
- Contact and self-help details or functionality are presented consistently when present on multiple web pages.
Guideline 3.3
Help users avoid and correct mistakes.
3.3.7 Redundant Entry
A 2.2
- Information that a user must re-enter to complete a single-session process must be auto-populated or available for the user to select, unless re-entering the information is essential to the functionality, the information poses security issues, or the previously-entered information is no longer valid.
3.3.8 Accessible Authentication (Minimum)
AA 2.2
- A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless the cognitive function test can be bypassed in some way, can be completed with assistance by some other mechanism, uses object recognition (such as "click on the photo of a flower"), or uses identification of non-text content provided by the user (such as a user-provided image).
3.3.9 Accessible Authentication (Enhanced)
AAA 2.2
- A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless the cognitive function test can be bypassed in some way or can be completed with assistance by some other mechanism.
This checklist is provided as a resource to help implement Web Content Accessibility Guidelines (WCAG) 2.2 (W3C Recommendation), which is Copyright © 2017-2023 W3C®.