Background

§1194.21(a) of Section 508 states that:

"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."

Take a moment to consider how a person with low or no vision would launch a software program from the desktop. How would that person resize a window or use a scroll bar? Having access to software controls through keyboard alternatives is essential for people who cannot accurately control a mouse or for users with a visual disability who do not use a mouse.

However, detailed procedures that require the fine level of control afforded by a pointing device, such as painting an image with a brush, picking a color, and actually drawing a design do not have to have keyboard controls associated with them. The Access Board, which provides guidance on the provisions, has offered this rationale:

"...providing keyboard alternatives for creating an image by selecting a "drawing tool", picking a color, and actually drawing a design would be extremely difficult. Such procedures require the precise level of control afforded by a pointing device and cannot be given text labels because there is no way to predict what action the user plans to perform." (http://www.access-board.gov)

A blind person can only interact with the system, or assistive technology, through the keyboard using keyboard substitutes or the accessibility options provided by Microsoft through the Operating System.

Keyboard or keypad commands provide a viable alternative for those who cannot use a pointing device or touch screen. Software that is designed to run on a kiosk and has a touch screen interface should also have a keyboard alternative that performs the same functionality as the touch screen.

Select the Next button to find out how to assess whether your application conforms to this provision.