Below is a list of Priority A and AA Guidelines added to WCAG 2.2 Web Content Accessibility Guidelines. Please note that previous guidelines from WCAG 2.1 are still in effect.
Page Content
Guideline 2.4: Navigable
Guideline 2.4.1-2.4.10 details
Guideline 2.4.11 Focus Not Obscured (Minimum) (AA)
Guideline Text (2.4.11)
When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content.
How to Implement 2.4.11
- Ensure that lightboxes, sticky footers, messages and headers, or other items do not cover the location of the keyboard focus.
See also Understanding Guideline 2.4.11
Guideline 2.5: Input Modalities
Make it easier for users to operate functionality through various inputs beyond keyboard.
New Guideline 2.5.7: Dragging Motions (AA)
Guideline Text (2.5.7)
How to Implement 2.5.7
Note: This affects users who may be using speech control, head pointers or other other mouse alternatives. It may also affect users not able to fully control a mouse.
- If an interface relies on dragging motions, provide a single pointer alternative (e.g. an initial tap "to establish a starting point", holding then releasing to provide an end point).
- Keyboard alternatives (e.g. use of arrow keys) or menu commands (e.g. file upload in lieu of drag and drop interfaces) can also be an accessible alternative.
- Exceptions are made when the dragging gesture is essential to the functionality of the tool.
See also Understanding Guideline 2.5.7
New Guideline 2.5.8: Target Size Minimum (AA)
Guideline Text (2.5.2)
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.
How to Implement 2.5.8
- Target elements of these guidelines include text links, buttons, icons, sliders and other elements that the user needs to "click on" or select.
- Minimum target sizes should be 24 by 24 pixels.
- If the size must be smaller, there should be a padding of 24 pixels around the element.
- If none of these are possible, a second alternate control meeting the guidelines should be available.
See also Understanding Guideline 2.5.8
Guideline 3.2: Predictable
Guideline 3.2.1 to 3.2.5 information
New Guideline 3.2.6: Consistent Help (A)
Guideline Text (3.2.6)
If a Web page contains any of the following help mechanisms, and those mechanisms are repeated on multiple Web pages within a set of Web pages, they occur in the same order relative to other page content, unless a change is initiated by the user:
- Human contact details;
- Human contact mechanism;
- Self-help option;
- A fully automated contact mechanism.
How to Implement 3.2.6
- Ensure that links to contact information, help forms, documentation and other forms of support are in the same location on a page throughout a Web site.
See also Understanding Guideline 3.2.6
Guideline 3.3: Input Assistance
Guideline 3.3.1 to 3.3.6 information
New Guideline 3.3.7: Redundant Entry (A)
Guideline Text (3.3.7)
Information previously entered by or provided to the user that is required to be entered again in the same process is either:
- auto-populated, or
- available for the user to select.
Except when:
- re-entering the information is essential,
- the information is required to ensure the security of the content, or
- previously entered information is no longer valid.
How to Implement 3.3.7
- Ensure that information entered in a previous step in a form carries over to the next step.
- Allow users to copy or confirm information with duplicate values within a form (e.g. billing address is the same as the shipping address). An option to override default values should be given.
- There are exceptions for security measures (e.g. entering passwords).
See also Understanding Guideline 3.3.7
New Guideline 3.3.8 Accessible Authentication (Minimum) (AA)
Guideline Text (3.3.8)
A cognitive function test (such as remembering a password or solving a puzzle) is not required for any step in an authentication process unless that step provides at least one of the following:
- Alternative
- Another authentication method that does not rely on a cognitive function test.
- Mechanism
- A mechanism is available to assist the user in completing the cognitive function test.
- Object Recognition
- The cognitive function test is to recognize objects.
- Personal Content
- The cognitive function test is to identify non-text content the user provided to the Web site
How to Implement 3.3.8
Note: This guideline is meant to help those who may have difficulty memorizing passwords.
- Avoid "cognitive function tests" for authentication.
Note: Memorized passwords or gestures are considered to be "cognitive function tests." - Instead of passwords consider:
- biometrics (e.g. facial/finger print recognition)
- verification codes generated by devices.
- object recognition (e.g. pick an image or other object)
- access to password managers
- send an access link to a registered email address
See also Understanding Guideline 3.3.8
Last Update: November 3, 2023