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 A)
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 A)
Can all site or application controls and content be accessed and operated through the use of a keyboard or keyboard interface with no exceptions? (Success Criterion 2.1.3 – Level AAA)
If web content uses time limits can a user turn off, adjust or extend those time limits? (Success Criterion 2.2.1 – Level A)
Can moving, blinking, scrolling or auto-updating content be paused, stopped or hidden by the user? (Success Criterion 2.2.2 – Level A)
Is your website/application free from time limits? (Success Criterion 2.2.3 – Level AAA)
Can users postpone or suppress server-side interruptions with the exception of those that involve an emergency? (Success Criterion 2.2.4 – Level AAA)
When re-authentication is required, is previously entered data retained? (Success Criterion 2.2.5 – Level AAA)
Have you ensured that your website/application does not contain content that flashes? (Success Criterion 2.3.1 – Level A)
Have you ensured that your website/application does not contain content that flashes? (Success Criterion 2.3.2 – Level AAA)
Is there a way for users to bypass content that is repeated on multiple web pages (e.g., setting controls, navigation areas, user menu, etc.)? (Success Criterion 2.4.1 – Level A)
Do all pages on your website have unique descriptive page titles? (Success Criterion 2.4.2 – Level A)
If page content is designed to be navigated sequentially, do the focusable parts receive focus in a sequential order that maintains the meaning and operation of the content? (Success Criterion 2.4.3 – Level A)
Is all link text contextual and provide users with a clear indication of the link destination and content? (Success Criterion 2.4.4 – Level A)
Does your website or application provide users with multiple ways to navigate to the site or applications individual content pages? (Success Criterion 2.4.5 – Level AA)
Does your web site or application use clear headings and labels that provide meaning and organization? (Success Criterion 2.4.6 – Level AA)
Does your website or application provide a visual focus indicator when navigating through content using the keyboard? (Success Criterion 2.4.7 – Level AA)
Can the user determine their location on your web site or application based on the page content, navigation, or other focus indicators? (Success Criterion 2.4.8 – Level AAA)
Can the purpose of all links on your website or application be determined by the link text alone? (Success Criterion 2.4.9 – Level AAA)
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 AAA)