Keyboard:
Understanding SC 2.1.1
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 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.
Intent of this Success Criterion
The intent of this Success Criterion 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.
Most actions carried out by a pointing device can also be done from the keyboard (for example, clicking, selecting, moving, sizing). However, there is a small class of input that is done with a pointing device that cannot be done from the keyboard in any known fashion without requiring an inordinate number of keystrokes. Free hand drawing, watercolor painting, and flying a helicopter through an obstacle course are all examples of functions that require path dependent input. Drawing straight lines, regular geometric shapes, re-sizing windows and dragging objects to a location (when the path to that location is not relevant) do not require path dependent input.
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).
It is assumed that the design of user input features takes into account that operating system keyboard accessibility features may be in use. For example, modifier key locking may be turned on. Content continues to function in such an environment, not sending events that would collide with the modifier key lock to produce unexpected results.
Specific Benefits of Success Criterion 2.1.1:
People who are blind (who cannot use devices such as mice that require eye-hand coordination)
People with low vision (who may have trouble finding or tracking a pointer indicator on screen)
Some people with hand tremors find using a mouse very difficult and therefore usually use a keyboard
Examples of Success Criterion 2.1.1
Example 1: A drawing Program.
A drawing program allows users to create, size, position and rotate objects from the keyboard.
Example 2: A drag and Drop Feature.
An application that uses drag and drop also supports "cut" and "paste" or form controls to move objects.
Example 3: Moving between and connecting discrete points.
A connect-the-dots program allows the user to move between dots on a screen and use the spacebar to connect the current dot to the previous one.
Example 4: Exception - Painting Program.
A watercolor painting program passes as an exception because the brush strokes vary depending on the speed and duration of the movements.
Example 5: Exception - Model helicopter flight training simulator.
A model helicopter flight training simulator passes as an exception because the nature of the simulator is to teach real-time behavior of a model helicopter.
Example 6: A PDA with an optional keyboard
A PDA device that is usually operated via a stylus has an optional keyboard that can be attached. The keyboard allows full Web browsing in standard fashion. The Web content is operable because it was designed to work with keyboard-only access.
Related Resources
Resources are for information purposes only, no endorsement implied.
(none currently documented)
Techniques and Failures for Success Criterion 2.1.1 - Keyboard
Each numbered item in this section represents a technique or combination of techniques that the WCAG Working Group deems sufficient for meeting this Success Criterion. However, it is not necessary to use these particular techniques. For information on using other techniques, see Understanding Techniques for WCAG Success Criteria, particularly the "Other Techniques" section.
Sufficient Techniques
Ensuring keyboard control by using one of the following techniques.
G90: Providing keyboard-triggered event handlers using one of the following techniques:
SCR20: Using both keyboard and other device-specific functions (Scripting)
SCR35: Making actions keyboard accessible by using the onclick event of anchors and buttons (Scripting)
SCR2: Using redundant keyboard and mouse event handlers (Scripting)
SL9: Handling Key Events to Enable Keyboard Functionality in Silverlight (Silverlight)
SL14: Providing Custom Control Key Handling for Keyboard Functionality in Silverlight (Silverlight)
FLASH17: Providing keyboard access to a Flash object and avoiding a keyboard trap (Flash) AND using the following techniques as applicable:
Additional Techniques (Advisory) for 2.1.1
Although not required for conformance, the following additional techniques should be considered in order to make content more accessible. Not all techniques can be used or would be effective in all situations.
Using XHTML role, state, and value attributes if repurposing static elements as interactive user interface components (future link) AND SCR29: Adding keyboard-accessible actions to static HTML elements (Scripting)
Providing keyboard shortcuts to important links and form controls (future link)
Using unique letter combinations to begin each item of a list (future link)
Choosing the most abstract event handler (future link) (Scripting)
Using the onactivate event (future link) (Scripting)
Avoiding use of common user-agent keyboard commands for other purposes (future link)
Common Failures for SC 2.1.1
The following are common mistakes that are considered failures of Success Criterion 2.1.1 by the WCAG Working Group.
Key Terms
- functionality
processes and outcomes achievable through user action
- keyboard interface
interface used by software to obtain keystroke input
Note 1: A keyboard interface allows users to provide keystroke input to programs even if the native technology does not contain a keyboard.
Example: A touchscreen PDA has a keyboard interface built into its operating system as well as a connector for external keyboards. Applications on the PDA can use the interface to obtain keyboard input either from an external keyboard or from other applications that provide simulated keyboard output, such as handwriting interpreters or speech-to-text applications with "keyboard emulation" functionality.
Note 2: Operation of the application (or parts of the application) through a keyboard-operated mouse emulator, such as MouseKeys, does not qualify as operation through a keyboard interface because operation of the program is through its pointing device interface, not through its keyboard interface.