Applets

Lotus Notes checkpoint 6.1

Provide alternate content for Java applets which are not accessible.

Rationale

When designing a Web application, the Java applets available in Domino can be used to display views, embedded outlines, action bars and rich text fields in a browser. The applets provide a visual interface which is more Notes-like. However, the applets are not accessible to anyone who is using the keyboard or assistive technology like a screen reader. These users will not be able to use the application because it is not accessible.

At this time, the keyboard cannot be used to give focus to an applet or to exit an applet once it has focus. Even if you follow the techniques in the IBM Java Accessibility Checklist for Java2 applets and the IBM Software Accessibility Checklist for all other Java 1.1.x applets, they will not have keyboard focus. Because of this problem, Java applets should not be used.

This checkpoint only applies to applications that will be deployed on the Web.

Development techniques

The following techniques are the minimum required to meet Checkpoint 6.1 from the Lotus Notes Accessibility Checklist.

Provide alternate text for the applet to describe the applet's function. Specify alternate text on the Basics tab of the Java applet Properties box.
To make views accessible on the Web open the view. Open the View Properties box and select the Advanced tab. In the For Web access section, select "Treat view contents as HTML".
To make an embedded view accessible on the Web, open the form or page which contains the view. Open the Embedded View Properties box and select the Info tab. In the Web access section, select "Using HTML" to indicate that the view applet should not be used.
To make embedded outlines accessible on the Web, open the form or page which contains the embedded outline. Open the Embedded Outline Properties box and select the Info tab. In the Web access section, select "Using HTML".
To make Action bars accessible on the Web, open the Action Bar Properties box. On the Action Bar Info tab, go to the Web Access section. Select "Using HTML".
To make rich text fields accessible on the Web, open the form containing the rich text field. Select the rich text field. Open the Field Properties box and select the Info tab. In the Web Access section, select "Using HTML".
To make Java applets accessible, follow the IBM Java Accessibility Checklist

Testing techniques

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

Tools

Install the following tools to test this checkpoint:

A Web accessibility checking tool.
A screen reader for testing java applets.
A screen reader to test applications that support the Domino Web user interface.

Techniques

*The following techniques are required to verify this checkpoint:*
	Action	Result
1.	Test each page of the application with a Web checking tool to verify that alt="text" attributes are used for applets.	Pass/Fail: See the instructions provided with your Web checking tool to verify applet alt text.
2.	Test the Web site with a screen reader that supports applets to determine if the applets are accessible. For more information, see the Java testing techniques. Use only the keyboard to navigate the controls. Exercise all applet or object functions with the screen reader.	Pass: The applet or object can be navigated using only the keyboard. All controls and content in the applet or object are read by the screen reader. Fail: One or more controls cannot be accessed using the keyboard. The content and/or controls are not read by the screen reader. If the content is not directly accessible, perform the next test to determine if an accessible alternative has been provided for the applet or object.
3.	If the Web site includes applets or objects that are not directly accessible, test with a screen reader to determine if an equivalent alternative has been provided and is accessible. Check the page for a link to an accessible alternative. Activate the link and verify the keyboard can be used to navigate the content. If the applet does not require user interaction, verify there is a text explanation for the applet content or a link to an accessible alternative. If the alternative to the applet is in HTML, verify that the content can be read by a screen reader.	Pass: The Web page includes a link to an accessible alternative for the applet. If the alternative is in HTML, the content can be read by a screen reader. The applet requires no user interaction and provides a text description of the applet. Fail: There are no accessible alternatives provided. There is a link to an alternative, but it is also not accessible.

Last updated February 08, 2008.

Checklist