WCAG 2.2 Operable

Question 1

2

Answer 1

2 Operable - User interface components and navigation must be operable.
- 2.1 Keyboard Accessible (2A, 1AAA)
- 2.2 Enough Time (2A, 4AAA)
- 2.3 Seizures and Physical Reactions (1A, 2 AAA)
- 2.4 Navigable (4A, 4AA, 5AAA - 2.4.11, 12 & 13 are New)
- 2.5 Input Modalities (4A, 2AA, 2AAA - 2.5.7 & 8 are New)

Question 2

2.1

Answer 2

2.1 Keyboard Accessible
Make all functionality available from a keyboard.
- 2.1.1 to 2.1.4

Question 3

2.1.1

Answer 3

2.1.1 Keyboard (Level A)
All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes, except where the underlying function requires input that depends on the path of the user’s movement and not just the endpoints.

Note 1
This exception relates to the underlying function, not the input technique. For example, if using handwriting to enter text, the input technique (handwriting) requires path-dependent input but the underlying function (text input) does not.

Note 2
This does not forbid and should not discourage providing mouse input or other input methods in addition to keyboard operation.

Question 4

2.1.2

Answer 4

2.1.2 No Keyboard Trap (Level A)
If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away.

Note
Since any content that does not meet this success criterion can interfere with a user’s ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference.

Question 5

2.1.3

Answer 5

2.1.3 Keyboard (No Exception) (Level AAA)
All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes.

Question 6

2.1.4

Answer 6

2.1.4 Character Key Shortcuts (Level A)
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:

Turn off
A mechanism is available to turn the shortcut off;
Remap
A mechanism is available to remap the shortcut to include one or more non-printable keyboard keys (e.g., Ctrl, Alt);
Active only on focus
The keyboard shortcut for a user interface component is only active when that component has focus.

Question 7

2.2

Answer 7

Enough Time - Provide users enough time to read and use content.
- 2.2.1 to 2.2.6

Question 8

2.2.1

Answer 8

2.2.1 Timing Adjustable (Level A)
For each time limit that is set by the content, at least one of the following is true:

Turn off
The user is allowed to turn off the time limit before encountering it; or

Adjust
The user is allowed to adjust the time limit before encountering it over a wide range that is at least ten times the length of the default setting; or

Extend
The user is warned before time expires and given at least 20 seconds to extend the time limit with a simple action (for example, “press the space bar”), and the user is allowed to extend the time limit at least ten times; or

Real-time Exception
The time limit is a required part of a real-time event (for example, an auction), and no alternative to the time limit is possible; or

Essential Exception
The time limit is essential and extending it would invalidate the activity; or

20 Hour Exception
The time limit is longer than 20 hours.

Question 9

2.2.2

Answer 9

2.2.2 Pause, Stop, Hide (Level A)
For moving, blinking, scrolling, or auto-updating information, all of the following are true:

Moving, blinking, scrolling
For any moving, blinking or scrolling information that (1) starts automatically, (2) lasts more than five seconds, and (3) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it unless the movement, blinking, or scrolling is part of an activity where it is essential; and

Auto-updating
For any auto-updating information that (1) starts automatically and (2) is presented in parallel with other content, there is a mechanism for the user to pause, stop, or hide it or to control the frequency of the update unless the auto-updating is part of an activity where it is essential.

Note 1
For requirements related to flickering or flashing content, refer to Guideline 2.3.

Note 2
Since any content that does not meet this success criterion can interfere with a user’s ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference.

Note 3
Content that is updated periodically by software or that is streamed to the user agent is not required to preserve or present information that is generated or received between the initiation of the pause and resuming presentation, as this may not be technically possible, and in many situations could be misleading to do so.

Note 4
An animation that occurs as part of a preload phase or similar situation can be considered essential if interaction cannot occur during that phase for all users and if not indicating progress could confuse users or cause them to think that content was frozen or broken.

Question 10

2.2.3

Answer 10

2.2.3 No Timing (Level AAA)
Timing is not an essential part of the event or activity presented by the content, except for non-interactive synchronized media and real-time events.

Question 11

2.2.4

Answer 11

2.2.4 Interruptions (Level AAA)
Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency.

Question 12

2.2.5

Answer 12

2.2.5 Re-authenticating (Level AAA)
When an authenticated session expires, the user can continue the activity without loss of data after re-authenticating.

Question 13

2.2.6

Answer 13

2.2.6 Timeouts (Level AAA)
Users are warned of the duration of any user inactivity that could cause data loss, unless the data is preserved for more than 20 hours when the user does not take any actions.

Note
Privacy regulations may require explicit user consent before user identification has been authenticated and before user data is preserved. In cases where the user is a minor, explicit consent may not be solicited in most jurisdictions, countries or regions. Consultation with privacy professionals and legal counsel is advised when considering data preservation as an approach to satisfy this success criterion.

Question 14

2.3

Answer 14

2.3 Seizures and Physical Reactions
Do not design content in a way that is known to cause seizures or physical reactions.
- 2.3.1 to 2.3.3

Question 15

2.3.1

Answer 15

2.3.1 Three Flashes or Below Threshold (Level A)
Web pages do not contain anything that flashes more than three times in any one second period, or the flash is below the general flash and red flash thresholds.

Note
Since any content that does not meet this success criterion can interfere with a user’s ability to use the whole page, all content on the Web page (whether it is used to meet other success criteria or not) must meet this success criterion. See Conformance Requirement 5: Non-Interference.

Question 16

2.3.2

Answer 16

2.3.2 Three Flashes (Level AAA)
Web pages do not contain anything that flashes more than three times in any one second period.

Question 17

2.3.3

Answer 17

2.3.3 Animation from Interactions (Level AAA)
Motion animation triggered by interaction can be disabled, unless the animation is essential to the functionality or the information being conveyed.

Question 18

2.4

Answer 18

2.4 Navigable - Provide ways to help users navigate, find content, and determine where they are.
- 2.4.1 to 2.4.13

Question 19

2.4.01

Answer 19

2.4.1 Bypass Blocks (Level A)
A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.

Question 20

2.4.10

Answer 20

(Level AAA)
Section headings are used to organize the content.

Note 1
“Heading” is used in its general sense and includes titles and other ways to add a heading to different types of content.

Note 2
This success criterion covers sections within writing, not user interface components. User interface components are covered under Success Criterion 4.1.2.

Question 21

2.4.11 [New]

Answer 21

2.4.11 Focus Not Obscured (Minimum)(Level AA) [New]
When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content.

Note 1
Where content in a configurable interface can be repositioned by the user, then only the initial positions of user-movable content are considered for testing and conformance of this Success Criterion.

Note 2
Content opened by the user may obscure the component receiving focus. If the user can reveal the focused component without advancing the keyboard focus, the component with focus is not considered hidden due to author-created content.

Question 22

2.4.12 [New]

Answer 22

2.4.12 Focus Not Obscured (Enhanced) (Level AAA) [New]
When a user interface component receives keyboard focus, no part of the component is hidden by author-created content.

Question 23

2.4.13 [New]

Answer 23

2.4.13 Focus Appearance (Level AAA) [New]
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.
Note 1
What is perceived as the user interface component or sub-component (to determine enclosure or size) depends on its visual presentation. The visual presentation includes the component’s visible content, border, and component-specific background. It does not include shadow and glow effects outside the component’s content, background, or border.

Note 2
Examples of sub-components that may receive a focus indicator are menu items in an opened drop-down menu, or focusable cells in a grid.

Note 3
Contrast calculations can be based on colors defined within the technology (such as HTML, CSS and SVG). Pixels modified by user agent resolution enhancements and anti-aliasing can be ignored.

Question 24

2.4.02

Answer 24

2.4.2 Page Titled (Level A)
Web pages have titles that describe topic or purpose.

Question 25

2.4.03

Answer 25

2.4.3 Focus Order (Level A)
If a Web page can be navigated sequentially and the navigation sequences affect meaning or operation, focusable components receive focus in an order that preserves meaning and operability.

Question 26

2.4.04

Answer 26

2.4.4 Link Purpose (In Context)(Level A)
The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context, except where the purpose of the link would be ambiguous to users in general.

Question 27

2.4.05

Answer 27

2.4.5 Multiple Ways (Level AA)
More than one way is available to locate a Web page within a set of Web pages except where the Web Page is the result of, or a step in, a process

Question 28

2.4.06

Answer 28

2.4.6 Headings and Labels(Level AA)
Headings and labels describe topic or purpose.

Question 29

2.4.07

Answer 29

2.4.7 Focus Visible(Level AA)
Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.

Question 30

2.4.08

Answer 30

2.4.8 Location(Level AAA)
Information about the user’s location within a set of Web pages is available.

Question 31

2.4.09

Answer 31

2.4.9 Link Purpose (Link Only)(Level AAA)
A mechanism is available to allow the purpose of each link to be identified from link text alone, except where the purpose of the link would be ambiguous to users in general.

Question 32

2.5

Answer 32

2.5 Input Modalities
Make it easier for users to operate functionality through various inputs beyond keyboard.
2.5.1 to 2.5.8
- 2.5.7 and 2.5.8 are New

Question 33

2.5.1

Answer 33

2.5.1 Pointer Gestures (Level A)
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.

Note
This requirement applies to web content that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).

Question 34

2.5.2

Answer 34

2.5.2 Pointer Cancellation (Level A)
For functionality that can be operated using a single pointer, at least one of the following is true:

No Down-Event
The down-event of the pointer is not used to execute any part of the function;

Abort or Undo
Completion of the function is on the up-event, and a mechanism is available to abort the function before completion or to undo the function after completion;

Up Reversal
The up-event reverses any outcome of the preceding down-event;

Essential
Completing the function on the down-event is essential.

Note 1
Functions that emulate a keyboard or numeric keypad key press are considered essential.

Note 2
This requirement applies to web content that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).

Question 35

2.5.3

Answer 35

2.5.3 Label in Name (Level A)
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.

Question 36

2.5.4

Answer 36

2.5.4 Motion Actuation (Level A)
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:

Supported Interface
The motion is used to operate functionality through an accessibility supported interface;
Essential
The motion is essential for the function and doing so would invalidate the activity.

Question 37

2.5.5

Answer 37

2.5.5 Target Size (Enhanced) (Level AAA)
The size of the target for pointer inputs is at least 44 by 44 CSS pixels except when:

Equivalent
The target is available through an equivalent link or control on the same page that is at least 44 by 44 CSS pixels;
Inline
The target is in a sentence or block of 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 to the information being conveyed.

Question 38

2.5.6

Answer 38

2.5.6 Concurrent Input Mechanisms (Level AAA)
Web content does not restrict use of input modalities available on a platform except where the restriction is essential, required to ensure the security of the content, or required to respect user settings.

Question 39

2.5.7 [New]

Answer 39

2.5.7 Dragging Movements (Level AA) [New]
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.

Note
This requirement applies to web content that interprets pointer actions (i.e. this does not apply to actions that are required to operate the user agent or assistive technology).

Question 40

2.5.8 [New]

Answer 40

2.5.8 Target Size (Minimum) (Level AA) [New]
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.

Note 1
Targets that allow for values to be selected spatially based on position within the target are considered one target for the purpose of the success criterion. Examples include sliders, color pickers displaying a gradient of colors, or editable areas where you position the cursor.

Note 2
For inline targets the line-height should be interpreted as perpendicular to the flow of text. For example, in a language displayed vertically, the line-height would be horizontal.