Documentation for accessibility features

Lotus Notes checkpoint 7.1

Provide documentation on all accessibility features, including keyboard access.

Rationale

People with disabilities cannot effectively use your application if they cannot access information on how to use accessibility features. This is particularly important for keyboard access. Since most applications focus on navigation with the mouse, it is not always clear how to use the application with the keyboard. All keyboard navigation that does not follow documented system conventions must be documented.

Keyboard navigation of embedded elements in R5 such as views, folders, outlines, navigators and date pickers can be difficult if more than one embedded element is included in a frame. The user must already know the page layout in order to navigate with the keyboard. Documenting keyboard access for applications which use multiple embedded elements is critical for users who cannot use the mouse.

Development techniques

The following techniques are the minimum required to meet Checkpoint 7.1 from the Lotus Notes Application Accessibility Checklist:

Provide a section where all accessibility features are documented. The on-line help documentation in Lotus Notes is a good example of this technique.
Provide a section where unique keyboard accessibility features are documented. If the application uses standard system keyboard commands for navigation, they do not have to be documented. The keyboard accessibility information could also be included as part of the general accessibility section.
If the application uses multiple embedded elements, provide keyboard instructions for navigating between the embedded elements in the frame.

The techniques above are required; the following techniques are recommended to enhance accessibility:

Include a keyword search and help topic item for accessibility.
When the application provides instructions for completing tasks using the mouse, include the instructions for doing those tasks using the keyboard.
Provide a "Keys Help" item in the Help menu to provide quick access to the keyboard accessibility information.

Testing techniques

Test the software to ensure that it complies with accessibility requirements.

Tools

There are no tools required to test this checkpoint:

Techniques

The following technique is **required** to verify this checkpoint:
	Action	Result
1.	Display the application documentation including the information in "About this Database" and "Using this Database". Review the sections on accessibility and keyboard support.	Pass: The documentation includes a specific section on Accessibility. If the application does not have unique accessibility features or keyboard commands, the section is not required, but recommended. Application unique keyboard commands are documented. For example, Alt-B is used in Lotus Notes R5 to navigate the Bookmark bar with the keyboard. That command is documented in the Notes Accessibility section under Keyboard Shortcuts. If the application only uses standard operating system keyboard commands, they do not need to be documented. Application accessibility features are documented. For example, Notes 6 provides an option to inherit system settings. This option is documented in the Accessibility section under user settings. If the application does not provide specific accessibility features, this section is not required. "How to" instructions using the mouse also include keyboard instructions when custom keyboard commands are used. If the operation can be done using standard operating system keyboard commands (e.g. Ctrl-P for Print), they do not need to be documented. Fail: The documentation does not include a section on Accessibility. The application uses unique keyboard commands are not documented. The application provides accessibility features or preferences that are not documented. "How to" instructions using the mouse do not include keyboard instructions and the operation cannot be completed using standard keyboard commands.

Last updated February 08, 2008.

Checklist