Operable
Users must be able to operate the interface (the interface cannot
require interaction that a user cannot perform).
User interface components and navigation must be operable. This means
that users must be able to operate the interface (the interface cannot
require interaction that a user cannot perform).
-
Make all functionality available from a
keyboard.
-
Give users enough time to read and use content.
- Do not use content that causes seizures.
- Help users navigate and find content.
20 Guidelines
Is your Content Operable?
The questions below are designed to assist you in determining if your
website, application, and/or content is operable to people with
disabilities. Each question is linked to in-depth information,
resources, and examples on how to apply the guidelines to our
products.
Are all website/application controls and content fully operable through a keyboard interface? (Success Criterion 2.1.1 – Level 1)
Can keyboard focus be moved into and out of web content and components without getting stuck in keyboard traps? (Success Criterion 2.1.2 – Level 1)
Are all website/application controls and content fully operable with no exceptions through a keyboard interface? (Success Criterion 2.1.3 – Level 3)
If web content uses time limits can a user turn off, adjust or extend those time limits? (Success Criterion 2.2.1 – Level 1)
Can moving, blinking, scrolling or auto-updating content be paused, stopped or hidden by the user? (Success Criterion 2.2.2 – Level 1)
Is your website/application free from time limits? (Success Criterion 2.2.3 – Level 3)
Can users postpone or suppress server-side interruptions with the exception of those that involve an emergency? (Success Criterion 2.2.4 – Level 3)
When re-authentication is required, is previously entered data retained? (Success Criterion 2.2.5 – Level 3)
Does any web content flash more than 3 times within a 1 second period, or the flash is below the general flash and red flash thresholds? (Success Criterion 2.3.1 – Level 1)
Does your web content contain anything that flashes more than 3 times within a 1 second period? (Success Criterion 2.3.2 – Level 3)
Is there a way for users to bypass blocks of content such as setting controls, large navigation areas, etc. that are repeated on multiple web pages? (Success Criterion 2.4.1 – Level 1)
Does every webpage have it’s own descriptive title? (Success Criterion 2.4.2 – Level 1)
Do focusable components of the content receive focus in a sequential order that is consistent and preserves meaning? (Success Criterion 2.4.3 – Level 1)
For each link in your web content, does the link text, or surrounding context provide definition of the purpose of the link? (Success Criterion 2.4.4 – Level 1)
In your web content, is there more than one way for a user to locate a web page within the site? (Success Criterion 2.4.5 – Level 2)
If your web content contains Headings and/or Labels, are they clear and descriptive? (Success Criterion 2.4.6 – Level 2)
In your web content, do all operable interfaces provide a visual focus indication when navigated to with the keyboard? (Success Criterion 2.4.7 – Level 2)
Can the user determine their location in a web site or web application based on the page content, navigation, or other indicators. (Success Criterion 2.4.8 – Level 3)
For each link in your platform/content, does the link text alone provide definition of the purpose of the link? (Success Criterion 2.4.9 – Level 3)
Are descriptive section headings provided for sections of lengthy content such as chapters and subchapters, topics and subtopics, etc? (Success Criterion 2.4.10 – Level 3)