Techniques for WCAG 2.0

Skip to Content (Press Enter)

-

G202: Ensuring keyboard control for all functionality

Important Information about Techniques

See Understanding Techniques for WCAG Success Criteria for important information about the usage of these informative techniques and how they relate to the normative WCAG 2.0 success criteria. The Applicability section explains the scope of the technique, and the presence of techniques for a specific technology does not imply that the technology can be used in all situations to create content that meets WCAG 2.0.

Applicability

All technologies that support interactive operation.

This technique relates to:

Description

The objective of this technique is to provide keyboard operation for all the functionality of the page. When all functionality of content can be operated through a keyboard or keyboard interface, it can be operated by those with no vision as well as by those who must use alternate keyboards or input devices that act as keyboard emulators like speech input software or on-screen keyboards.

A keyboard interface allows users to provide keystroke input to programs even if the computing device that they are using does not contain a hardware keyboard. For example, many mobile devices have keyboard interfaces within their operating system as well the option to connect external wireless keyboards. Applications can use the interface to obtain keyboard input either from an external keyboard or from other services that provide simulated keyboard output, such as switch devices, handwriting interpreters or speech-to-text applications.

To implement this technique, first determine what functionality is available to users on the page. In this step, it is important to consider functions performed using both the mouse and the keyboard together. Examples of functionality include the use of physical controls such as links, menus, buttons, checkboxes, radio buttons and form fields as well as the use of features like drag and drop, selecting text, resizing regions or bringing up context menus. Other examples of functionality may based on tasks such as adding or removing an item from a shopping cart or initiating a chat session with a sales representative.

Once the functionality of the content has been determined, the author verifies that each of the functions identified can be performed using only the keyboard.

Note: This does not necessarily mean that each of the individual controls can be used from the keyboard as long as there are multiple methods to perform the same function available on the page. Authors are advised to consider how users will discover any keyboard equivalents which are available.

Examples

Tests

Procedure

  1. Identify all functionality on the content.

  2. Check that all functionality can be accessed using only the keyboard or keyboard interface.

Expected Results

If this is a sufficient technique for a success criterion, failing this test procedure does not necessarily mean that the success criterion has not been satisfied in some other way, only that this technique has not been successfully implemented and can not be used to claim conformance.