|
|
|
|
|
Keyboard Accessible
Guideline
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 (WCAG 2.1.1). 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 the method for moving focus away (WCAG 2.1.2).
Intent
The intent of this requirement is to ensure that, wherever possible, content can be operated through a keyboard or keyboard interface (so an alternate keyboard can be used). When content can be operated through a keyboard or alternate keyboard, it is operable by people with no vision (who cannot use devices such as mice that require eye-hand coordination) as well as by people who must use alternate keyboards or input devices that act as keyboard emulators. Keyboard emulators include speech input software, sip-and-puff software, on-screen keyboards, scanning software and a variety of assistive technologies and alternate keyboards. Individuals with low vision also may have trouble tracking a pointer and find the use of software much easier (or only possible) if they can control it from the keyboard.
Examples of "specific timings for individual keystrokes" include situations where a user would be required to repeat or execute multiple keystrokes within a short period of time or where a key must be held down for an extended period before the keystroke is registered.
The phrase "except where the underlying function requires input that depends on the path of the user's movement and not just the endpoints" is included to separate those things that cannot reasonably be controlled from a keyboard.
The use of MouseKeys would not satisfy this Success Criterion because it is not a keyboard equivalent to the application; it is a mouse equivalent (i.e., it looks like a mouse to the application).
Finding Applicable Components
Find all visible and hidden interactive interface components (links, form fields, drop down menus, show/hide content, tree views, pop ups/light boxes, frames, iframes, etc.) using a mouse (hover and/or click).
Inspecting and Using Components
Using standard keyboard commands (Tab, [Shift+Tab], Space bar, ALT, arrow keys, Enter, etc.), navigate through each interactive interface component (including form drop-down lists and form fields) and activate all interface components.
Where standard keyboard commands do not work, there must be instructions for extending standard keyboard command operations (e.g., getting out of a keyboard "trap") and/or remapped/alternate keys. The non-standard keyboard commands cannot interfere with JAWS keyboard shortcuts.
Inspect any help (contextual help or application help) and documentation for notification of available Alternate keyboard commands (e.g., non-standard keyboard controls for all users, or access keys, hotkeys). Verify that non-standard keyboard commands they can be used to address deficiencies found in step a.
Where additional information is provided through the TITLE attribute on interactive components (eg., tool-tip), verify that information can be revealed by keyboard or is conveyed through screen text or visual context.
Section 508/WCAG 2.0 Failure Conditions
- An interactive interface component or function cannot be accessed by the keyboard.
- Fails 1194.21(a): Keyboard Accessibility.
- Fails 2.1.1 Keyboard
- An interactive interface component or function cannot be activated by the keyboard.
- Fails 1194.21(a): Keyboard Accessibility.
- Fails 2.1.1 Keyboard
- A "keyboard trap" disrupts keyboard navigation.
- Fails 1194.21(a): Keyboard Accessibility.
- Fails 2.1.2 No Keyboard Trap.
- Interactive interface components and functions can be accessed AND/OR activated by the keyboard BUT non-standard/Alternative commands are undocumented.
- Fails 1194.21(a): Keyboard Accessibility.
- Fails 1.3.1 Info and relationships.
Reporting Test Results
Any failure in Section 508 Failure Conditions results in: Fails Baseline Requirement #1.
All interactive interface components and functions can be accessed AND activated by the keyboard, AND any non-standard/ Alternative commands are documented results in: Passes Baseline Requirement #1.
See Also |