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.

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.

  • Keyboard - Are all website/application controls and content fully operable through a keyboard interface? (Success Criterion - 2.1.1 - Level A)
  • No Keyboard Trap - 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)
  • Keyboard (No Exception) - 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)
  • Character Key Shortcuts - Still need question (Success Criterion - 2.1.4 - Level A)
  • Timing Adjustable - If web content uses time limits can a user turn off, adjust or extend those time limits? (Success Criterion - 2.2.1 - Level A)
  • Pause, Stop, Hide - Can moving, blinking, scrolling or auto-updating content be paused, stopped or hidden by the user? (Success Criterion - 2.2.2 - Level A)
  • No Timing - Is your website/application free from time limits? (Success Criterion - 2.2.3 - Level AAA)
  • Interruptions - Can users postpone or suppress server-side interruptions with the exception of those that involve an emergency? (Success Criterion - 2.2.4 - Level AAA)
  • Re-authenticating - When re-authentication is required, is previously entered data retained? (Success Criterion - 2.2.5 - Level AAA)
  • Timeouts - Still need question (Success Criterion - 2.2.6 - Level AAA)
  • Three Flashes or Below Threshold - Have you ensured that your website/application does not contain content that flashes? (Success Criterion - 2.3.1 - Level A)
  • Three Flashes - Have you ensured that your website/application does not contain content that flashes? (Success Criterion - 2.3.2 - Level AAA)
  • Animation from Interactions - Still need question (Success Criterion - 2.3.3 - Level AAA)
  • Bypass Blocks - 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)
  • Section Headings - 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)
  • Page Titled - Do all pages on your website have unique descriptive page titles?  (Success Criterion - 2.4.2 - Level A)
  • Focus Order - 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)
  • Link Purpose (In Context) - 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)
  • Multiple Ways - 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)
  • Headings and Labels - Does your web site or application use clear headings and labels that provide meaning and organization? (Success Criterion - 2.4.6 - Level AA)
  • Focus Visible - Does your website or application provide a visual focus indicator when navigating through content using the keyboard? (Success Criterion - 2.4.7 - Level AA)
  • Location - 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)
  • Link Purpose (Link Only) - 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)
  • Pointer Gestures - Still need question (Success Criterion - 2.5.1 - Level A)
  • Pointer Cancellation - Still need question (Success Criterion - 2.5.2 - Level A)
  • Label in Name - Still need question (Success Criterion - 2.5.3 - Level A)
  • Motion Actuation - Still need question (Success Criterion - 2.5.4 - Level A)
  • Target Size - Still need question (Success Criterion - 2.5.5 - Level AAA)
  • Concurrent Input Mechanisms - Still need question (Success Criterion - 2.5.6 - Level AAA)