Skip to main content

Keyboard equivalents for navigators

Lotus Notes checkpoint 1.1

Provide keyboard equivalents for all navigator actions.

Rationale

Techniques

Testing

 

Rationale

Navigators provide a graphical display of folders, views and design elements to make it easier for some users to find information. However, navigators cannot be accessed without the use of a mouse, so the information is inaccessible to anyone who must use the keyboard. To make navigators accessible to someone who cannot use the mouse, provide an alternative method to accomplish the same function.

Back to top

Development techniques

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

  • Instead of using navigators, use one or more of the following accessible navigation methods:
    • Folder Pane. The Folder Pane is the standard navigation structure available in Notes that was commonly used in Notes 4.x applications.
    • Outlines. Outlines provide more control over how elements are displayed in a navigation pane for a more custom navigation look. Outlines are programmable and customizable so you can control the look of the outline while maintaining accessibility. The database templates provided with Lotus Notes use outlines for navigation. NOTE: Do not display outlines on the Web using the Java applet. Outlines displayed using the Java applet are not accessible.
    • Frames. Framesets and imagemaps can also be used to provide accessible navigation. The frameset is accessible if a title has been provided for each frame in the frameset. Programmable hotspots on the imagemap can perform an action when selected by a user, but alternate text must be provided for each area of the map to make it accessible.
  • If navigators are used, provide equivalent functions through the Actions menu. For example:
    • List navigator views in the View menu. When the view is created, check the option "Show in View menu". The name of the view must be consistent with the name of the action on the navigator or it is not accessible. A user can access the navigator view actions by going to the Actions menu, entering View-Go To and then selecting the view corresponding to the navigator action.
    • List navigator actions (e.g. creating documents, opening links) in the Actions or Create menu. For example, if the navigator has an option "Submit a change request", there must be an action titled "Submit a change request" in the Actions menu with the same function.
    • If an application uses a full screen navigator, the Actions menu is not available from the navigator screen. In addition to making the views and actions available from the Actions menu, an additional step must be taken to provide equivalent function. Create a special view with the name "Instructions for users with disabilities" and check the option "Show in View menu" in the View properties box. The view must contain one document that describes how to access the navigator views and actions using the keyboard. When this view is selected, the default Folder Pane is displayed providing accessible navigation to the View, Actions and Create menus.
    • Document how to access navigator functions with the keyboard using the Actions menu in the "Help Using This Database" document.

Back to top


Testing techniques

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

Tools

No tools are required to test this checkpoint.

Techniques

The following techniques are required to verify this checkpoint:
  Action Result
1. Manually verify all navigator actions are available using only the keyboard:

  • If the navigator action opens a view, verify there is a view with the same name listed in the View menu by typing View-Go To and opening the view.
  • If the navigator action creates a document, verify there is an action in the Create or Actions menu with the same name.
  • If the navigator action performs other functions, verify there are actions with the same name in the Actions menu that perform the same function.
 Pass:

  • All navigator functions can be performed with the keyboard using an accessible alternative.

Fail:
  • One or more navigator actions are not available using the keyboard.
2. Verify the on-line help provides instructions for navigating the application using keyboard alternatives to the navigator. Pass:

  • The on-line help documents how to use the keyboard to access functions available through the navigator.

Fail:
  • The on-line help does not document how to access function accessible alternatives to the navigator.

Back to top


©2001, 2008 IBM Corporation

Last updated February 08, 2008.

 

Checklist

Next