🏹Operable
Operable ⚙️
User interface components and navigation must be operable:
Make all functionality accessible from keyboard ⌨️
Give users enough time to read and use content ⏳
Avoid content that causes seizures 💥
Help users navigate and find content 🔍
Keyboard Accessible
Make all functionality available from a keyboard.
Success Criterion 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
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
This does not forbid and should not discourage providing mouse input or other input methods in addition to keyboard operation.
Success Criterion 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.
Success Criterion 2.1.3 Keyboard (No Exception)§
Understanding Keyboard (No Exception) | How to Meet Keyboard (No Exception)
(Level AAA)
All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes.
Success Criterion 2.1.4 Character Key Shortcuts§
Understanding Character Key Shortcuts | How to Meet 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 use one or more non-printable keyboard characters (e.g. Ctrl, Alt, etc);
Active only on focus
The keyboard shortcut for a user interface component is only active when that component has focus.
Enough Time
Provide users enough time to read and use content.
Success Criterion 2.2.1 Timing Adjustable§
Understanding Timing Adjustable | How to Meet 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.
Note
This success criterion helps ensure that users can complete tasks without unexpected changes in content or context that are a result of a time limit. This success criterion should be considered in conjunction with Success Criterion 3.2.1, which puts limits on changes of content or context as a result of user action.
Success Criterion 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
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
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.
Success Criterion 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.
Success Criterion 2.2.4 Interruptions
(Level AAA)
Interruptions can be postponed or suppressed by the user, except interruptions involving an emergency.
Success Criterion 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.
Success Criterion 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.
Seizures and Physical Reactions
Do not design content in a way that is known to cause seizures or physical reactions.
Success Criterion 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.
Success Criterion 2.3.2 Three Flashes§
(Level AAA)
Web pages do not contain anything that flashes more than three times in any one second period.
Success Criterion 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.
Navigable
Provide ways to help users navigate, find content, and determine where they are.
Success Criterion 2.4.1 Bypass Blocks§
(Level A)
A mechanism is available to bypass blocks of content that are repeated on multiple Web pages.
Success Criterion 2.4.2 Page Titled§
(Level A)
Web pages have titles that describe topic or purpose.
Success Criterion 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.
Success Criterion 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.
Success Criterion 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.
Success Criterion 2.4.6 Headings and Labels§
(Level AA)
Headings and labels describe topic or purpose.
Success Criterion 2.4.7 Focus Visible§
(Level AA)
Any keyboard operable user interface has a mode of operation where the keyboard focus indicator is visible.
Success Criterion 2.4.8 Location§
(Level AAA)
Information about the user's location within a set of Web pages is available.
Success Criterion 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.
Success Criterion 2.4.10 Section Headings
(Level AAA)
Section headings are used to organize the content.
Note
"Heading" is used in its general sense and includes titles and other ways to add a heading to different types of content.
Input Modalities
Make it easier for users to operate functionality through various inputs beyond keyboard.
Success Criterion 2.5.1 Pointer Gestures§
(Level A)
All functionality that uses multi-point or path-based gestures for operation can be operated with a single pointer without a path-based gesture, unless a multi-point 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).
Success Criterion 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
Functions that emulate a keyboard or numeric keypad key press are considered 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).
Success Criterion 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.
Success Criterion 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.
Success Criterion 2.5.5 Target Size
(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.
Success Criterion 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.
Last updated