|
Introduction
This module will focus on ensuring that all actions that can be identified or labeled with text can be performed from a keyboard.
The Section 508 requirement covering this is: §1194.21 (a) When software is designed to run on a system that has a keyboard, product functions shall be executable from a keyboard where the function itself or the result of performing a function can be discerned textually.
People who have difficulty holding or controlling a mouse or other pointing device may find it more efficient to use a keyboard as their method of input. Screen reader users navigate through the screens of an application using keystrokes rather than a mouse.
When all of the features and controls in an application can be performed from a keyboard, many people who are unable to use a mouse or other pointing device are able to use the product. Controls and features must be labeled with text, and there must be a way to access and use each one with the keyboard alone. An exception to this requirement would be for features and controls such as drawing applications and programs that require specific mouse movements that cannot be achieved with the keyboard.
Features and controls that need keyboard access include:
- Context menus
- Drop-down lists
- Toolbar functionality
- Editing features such as select, copy, cut, paste
- Window movement and resizing
- Meaningful rollover content
- Navigation between panes
If the activation of a feature or control results in an element that can be identified with text, the result must also be labeled with text, and its controls must be accessible from the keyboard.
This requirement is not intended to prohibit or discourage the use of mouse-only functions in an application. There are many users, including users with disabilities, who want or need to use a mouse. The goal is to provide device-independent support that includes keyboard access as one method of interacting with an application's functionality.
In this module you will learn about ways that keyboard access can be provided in an application, and how to test for it.
Remember, both testers and developers can use the checkpoints for this requirement to be sure the products they are working with will be accessible to users with disabilities, including those using assistive technology (AT).
Use the link above to look at the checkpoints now. You may wish to keep the window open as a reference to use as you complete this module.
Video Overview of this Requirement
There are two videos that support the instruction on this requirement with additional information that may be helpful to testers and developers.
To view an approximately four and one-half minute overview video about the requirement, select the video link below. The video will open in a new window; if you are using a screen reader to take this training, press Enter when you hear, "To start, press Play button."
The second video, of approximately five minutes, includes examples created for developers working in the VA's Delphi environment; they do have general applicability to testing and developing other software applications. The video will open in a new window; if you are using a screen reader to take this training, press Enter when you hear, "To start, press Play button."
Select Next for an example.
| 
