translate
  1. Functional Accessibility Requirements
  2. 9. Web
  3. 9.2. Web content requirements
  4. 9.2.15: Keyboard

9.2.15: Keyboard

Where ICT is a web page, it shall satisfy WCAG 2.0 Success Criterion 2.1.1 Keyboard.

WCAG 2.0 success criterion: 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.

NOTE 1: 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 2: This does not forbid and should not discourage providing mouse input or other input methods in addition to keyboard operation.

Testing methods

Type of compliance Inspection
Pre-conditions
  1. The ICT is a web page.
Procedure
  1. Check that the web page does not fail WCAG 2.0 Success Criterion 2.1.1 Keyboard.
Result Pass: Check 1 is true
Fail: Check 1 is false

There is currently no content classified with this term.

Components that implement this clause

react-a11y-select

by mdesjardins

React select component with a focus on accessibility

The image reorderer component

Infusion Reorderer component

The Infusion Reorderer component allows developers to create rich, accessible user interfaces which enables users to directly re-arrange content on the page.

 

The inline edit component used for the title and description in a chart authoring interface

Infusion Inline Edit component

Inline Edit allows a user to do quick edits to simple text without having to switch modes or screens.

Accessible HTML5 Video Player with shortcuts

AFB Accessible Html5 Video Player

Fully accessible, embedded video player with HTML5 controls.