What's New in WCAG 2.1 & 2.2
WCAG 2.1
There are 12 new A & AA success criteria in WCAG 2.1:
# |
Name |
Description |
---|---|---|
1.3.4 |
Content does not restrict its view and operation to a single display orientation, such as portrait or landscape, unless a specific display orientation is essential. |
|
1.3.5 |
The purpose of each input field collecting information about the user can be programmatically determined when the input field serves a purpose identified in the Input Purposes for User Interface Components, such as name, title, organization, address, telephone, email, username, password, and credit card information. |
|
1.4.10 |
Content can be presented without loss of information or functionality, and without requiring scrolling in two dimensions for:
Except for parts of the content which require two-dimensional layout for usage or meaning, such as maps, diagrams, videos, and data tables. |
|
1.4.11 |
The visual presentation of the following have a contrast ratio of at least 3:1 against adjacent color(s):
|
|
1.4.12 |
In content implemented using markup languages that support the following text style properties, no loss of content or functionality occurs by setting all of the following and by changing no other style property:
Exception: Human languages and scripts that do not make use of one or more of these text style properties in written text can conform using only the properties that exist for that combination of language and script. |
|
1.4.13 |
Where receiving and then removing pointer hover or keyboard focus triggers additional content to become visible and then hidden, the following are true:
|
|
2.1.4 |
If a keyboard shortcut is implemented in content using only letter (including upper- and lower-case letters), punctuation, number, or symbol characters, then at least one of the following is true:
|
|
2.5.1 |
All functionality that uses multipoint or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multipoint or path-based gesture is essential. |
|
2.5.2 |
For functionality that can be operated using a single pointer, at least one of the following is true:
|
|
2.5.3 |
For user interface components with labels that include text or images of text, the name contains the text that is presented visually. NOTE: A best practice is to have the text of the label at the start of the name. |
|
2.5.4 |
Functionality that can be operated by device motion or user motion can also be operated by user interface components and responding to the motion can be disabled to prevent accidental actuation, except when:
|
|
4.1.3 |
In content implemented using markup languages, status messages can be programmatically determined through role or properties such that they can be presented to the user by assistive technologies without receiving focus. |
WCAG 2.2
There are 6 new A & AA success criteria in WCAG 2.2:
# |
Name |
Description |
---|---|---|
2.4.11 |
When a user interface component receives keyboard focus, no part of the component is hidden by author-created content. |
|
2.5.7 |
All functionality that uses a dragging movement for operation can be achieved by a single pointer without dragging, unless dragging is essential or the functionality is determined by the user agent and not modified by the author. |
|
2.5.8 |
The size of the target for pointer inputs is at least 24 by 24 CSS pixels, except where:
|
|
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:
|
|
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:
Except when:
|
|
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:
|