jump to content jump to navigation jump to links
IRS logo Section 508 for Software Development
Page 3 of 10    Training Previous Home Next
Help
Resources
Topic Menu
Module Introduction
Software Accessibility Guidelines
508 Conformance Evaluation Methodologies
Provision A
Provision B
Provision C
Provision D
Provision E
Provision F
Provision G
Provision H
Provision I
Provision J
Provision K
Provision L
Module Conclusion

Provision A

Development and Remediation Guidelines

As §1194.21(a) specifies, software should be designed so that it is fully functional while using the keyboard. Mouse support should be considered optional, instead of the other way around, since users with motor or visual disabilities may not use a mouse.

The Windows Operating System provides provision keyboard equivalents for general interface behavior, such as navigating among controls and windows, activating controls, adjusting window and region sizes, and scrolling controls and windows. Software should be designed so it does not override this built-in behavior.

For details on the Microsoft Windows built-in key combinations, you can view the Microsoft Keyboard Guide at http://www.microsoft.com/enable/products/altkeyboard.aspx.

Select the Next button to continue.