Efficient keyboard access is provided to application features.
Keyboard access does not override existing accessibility features.
The application provides more than one method to perform keyboard tasks whenever possible.
There are no awkward reaches for frequently performed keyboard operations.
The application does not use repetitive, simultaneous key presses.
The application provides keyboards equivalents for all mouse functions.
The application does not use any general navigation functions to trigger operations.
All the keyboard invoked menus, windows, and tool tips appear near the object they relate to.
There are no hard-coded graphical attributes, such as, lines, borders, or shadow thickness.
There are descriptive names for all application program interface (API) objects.
All multi-color graphical elements can be adjusted to monochrome only, whenever possible.
All interactive graphical user interface (GUI) elements are easily identifiable.
An option to turn off graphical backdrops has been provided.
All label objects have names that make sense when taken out of context.
There are no label names that have been used more than once in the same window.
There is consistency with label positioning throughout the application.
An alternative to what you see is what you get (WYSIWYG) is provided.
The following are guidelines for audio output. Using a screen reader, confirm that:
The following are guidelines for writing accessible documentation: