Web checklist

Applet and plug-in technologies were developed to deliver non-html coded content to enhance visual, audio, interactive effects, and to deliver other applications in the browser environment. HTML version 4 introduced the OBJECT element as a standard means for encoding other applications. When a Web site or Web application requires execution of these technologies in order to successfully complete tasks or to interpret content, it is important that both the informational content and the user interface be accessible to assistive technologies. In some cases, the user interface and the informational content are part of the same applet, plug-in, or application. For example, Java applets and Flash plug-ins present the user interface as part of the content. In other cases, the user interface is separate from the content. Multimedia plug-ins such as QuickTime, Real Audio, and Windows Media Player; and document reader plug-ins such as Acrobat Reader, have a separate player user interface (play, stop, fast forward, etc.) that controls the playing of the audio, video, or document content.

Compliance with this checkpoint requires all of the following techniques be met.

1. Make content accessible: Make the applet or object user interface programming and content directly accessible following the Software accessibility checklist.

Note: If you are developing with Flash or Flex, we have incorporated the Software accessibility checkpoints into the Web accessibility checklist. Please follow the Flash Accessibility techniques in the Web checklist only.

Examples for Adobe® Flash® developers

1. Make content accessible: Make the applet or object user interface programming and content directly accessible following the Software Accessibility checklist.

Checkpoint 2.1c Applets, Plug-ins, and Non-HTML content require that the Flash content comply with the Software accessibility checklist. The Software accessibility checklist contains checkpoints which Flash cannot comply with, specifically Software checkpoint 4.5 System settings for font size and color, and Software checkpoint 4.3 Support system settings for high contrast. Therefore, in order to claim compliance with Checkpoint 2.1c in the Web accessibility checklist, Flash must provide a directly accessible alternative to the Flash content.

Back to top

Examples for IBM® Lotus® Domino® developers

1. Make content accessible: Make the applet or object user interface programming and content directly accessible following the Software accessibility checklist.

Provide HTML alternatives for all default Java applets shipped with Domino. 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.

To comply with this technique, all of the following examples must be implemented.

Example 1

To make views accessible on the Web, open the View Properties box and select the Advanced tab. In the For Web access section, select "Treat view contents as HTML".

Example 2

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.

Example 3

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".

Example 4

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".

Example 5

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".

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

1. If using a plug-in, select a format that has extensive browser support and provide a link to the source file so the user may choose to launch it separately in an accessible player. For example, a Web browser may automatically launch .wav, .rm, .mov, and .txt files.

2. If using an object element, include equivalent HTML in the content of object element. When the object is not supported by the browser or by the assistive technology being used, the HTML content in the object element is rendered by the browser or made available to the assistive technology.

In the following example, the function of the gravity object is explained in the text following the open object tag. Since the function of the gravity object does not require user interaction, the text explanation is an accessible equivalent:

<object classid="java:gravity:class" width="200" height="250"> When gravity acts on an object, the weight... </object>

The following example shows that content of an object element can be another nested object. The nesting of objects allows the author to specify the order in which the browser should attempt to render the object's contents. The HTML 4.01 Specification on the object element (link resides outside of ibm.com) provides an example of an object that is a software applet. If that software applet is not supported (configured not to be supported, wrong platform, not installed, etc.) by the browser, the browser will attempt to render the contents of the object, which in this example is a nested object of an MPEG video. If the MPEG video is not supported, then the browser will open the next nested object, which is an animated gif. And finally, if that is not supported, the browser will open the next nested object, which in this example is a text description.

<!-- First, try the software applet -->
  <object title="IBM sites around the world"
    classid="ibmworld.class">
      <!-- Else, try the MPEG video -->
  <object data="ibmworld.mpeg" type="application/mpeg">
      <!-- Else, try the animated GIF -->
  <object data="ibmworld.gif" type="image/gif">
      <!-- Else render the text -->
 <p><strong>IBM </strong> is located in the following countries:
   Argentina, Australia, ... Vietnam.</p>
  </object>
  </object>
 </object>

The following test tools and techniques are required to test this checkpoint.

1. Test tools
2. Required accessibility verification test techniques