Test for accessibility using available tools.
Rationale
Accessibility must be included as part of the product test cycle to ensure people with disabilities can use the application.
Testing techniques
To satisfy Checkpoint 7.1, every checkpoint in the Lotus Notes Application Accessibility Checklist must be tested. Specific details on how to test the checkpoints are described on the techniques page for each checkpoint.
Be aware that a Lotus Notes application on a Domino server might be set up to be accessed either as a Lotus Notes Client application or as a Web application that uses a Web browser as the user interface. Some of the checkpoints in this checklist apply only if the Web interface is supported by the application. Read each checkpoint carefully to determine whether it applies to your application.
Links to each checkpoint techniques page are listed below.
- Checkpoint 1.1: Provide keyboard equivalents for all navigator actions.
- Checkpoint 1.2: Provide methods for skipping over navigation links to get to the main content of the Web page..
- Checkpoint 1.3: Provide a title for each frame.
- Checkpoint 2.1: Include all action buttons in the appropriate menu.
- Checkpoint 2.2: Provide text labels for all buttons.
- Checkpoint 3.1: Provide alternate text for important graphics.
- Checkpoint 3.2: Provide alternate text for image maps and image map hotspots.
- Checkpoint 3.3: Make text pop-ups accessible or provide an alternative.
- Checkpoint 4.1: Include views in the View menu if the application uses navigators.
- Checkpoint 4.2: Use color as an enhancement, not as the only way to convey information or indicate an action.
- Checkpoint 4.3: Provide a visible selector for embedded outlines and views.
- Checkpoint 5.1: Include forms in the appropriate action menu.
- Checkpoint 5.2: Provide short field help for all editable fields on the form.
- Checkpoint 5.3: Provide a descriptive title for each form and page.
- Checkpoint 5.4: Avoid the use of animated tables.
- Checkpoint 5.5: Use the TH element to mark up table heading cells. Use the headers attribute on cells of complex data tables.
- Checkpoint 5.6: Avoid the use of rich text lite fields.
- Checkpoint 6.1: Provide alternate content for Java applets which are not accessible.
- Checkpoint 6.2: Provide content for JavaScript which is keyboard accessible. If the content is not accessible, provide an alternative.
- Checkpoint 6.3: Web pages must be readable without requiring style sheets.
- Checkpoint 6.4: When HTML content is added to Domino applications, follow the IBM Web Accessibility Checklist guidelines.
©2001, 2008 IBM Corporation
Last updated February 07, 2008.