These articles provide practical advice on how to write your web content so that it conforms to the success criteria outlined in the Operable principle of the Web Content Accessibility Guidelines (WCAG) 2.0 and 2.1. Operable states that user interface components and navigation must be operable.
Easy to operate User interface components and navigation must be operable: The interface cannot require interaction that a user cannot perform. Under this principle you will find guidelines relating but not limited to: Keyboard Accessible: Make all functionality available from a keyboard. Enough Time: Provide users enough time to read and use content. Seizures and Physical …
2.1.1 Keyboard: 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. (Level A) Note 1: This exception relates to the underlying function, not the input …
2.1.2 No Keyboard Trap: 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 …
2.1.4 Character Key Shortcuts: 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: (Level A) Turn off: A mechanism is available to turn the shortcut off; Remap: A mechanism is available to remap the …
2.2.1 Timing Adjustable: For each time limit that is set by the content, at least one of the following is true: (Level A) 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 …
2.2.2 Pause, Stop, Hide (A): For moving, blinking, scrolling, or auto-updating information, all of the following are true: (Level A) 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 …
2.3.1 Three Flashes or Below Threshold: 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. (Level A). This applies to native apps by replacing “Web pages” with “Apps”. Requirements Content does not flash more than …
2.4.1 Bypass Blocks: A mechanism is available to bypass blocks of content that are repeated on multiple Web pages. (Level A)This applies to native apps by replacing “Web pages” with “screens”. Requirements (Web only) A “Skip to content” link is provided, allowing users to move the keyboard focus directly to the main content area; The “Skip to …
2.4.2 Page Titled: Web pages have titles that describe topic or purpose. (Level A)This applies to native apps by replacing “Web pages” with “Screens”. Requirements Each page has a title that is unique within the app/website. Each page has a title that indicates its topic or purpose. Why is it important? This ensures that people …
2.4.3 Focus Order: 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. (Level A)This applies to native apps by replacing “Web page” with “screen”. Requirements When navigated sequentially using a keyboard, interactive elements should receive focus following a …
