Applets and Plug-Ins

Accessibility Standards Checklist

Requirement

Provide alternate content for applets, plug-ins, or other applications which are not directly accessible. Information provided through a plug-in or applet must provide a link to the plug-in or applet used.

Reason

Applets are programs designed to be executed or launched from within a Web page. Simple applets can be compatible with screen readers, magnifiers, and other assisting technologies when the user interface is made up of only standard system controls that are supported by assisting technologies. Most text browsers, such as Lynx, and most assisting technologies, such as IBM Home Page Reader, do not support applets. Even when the browser and assisting technology combination support running applets, the content and programming could be implemented in a way that makes it inaccessible to the user. Typically the problem is when the applet uses non-standard controls or when the applet programming extends standard controls to create a custom look.

Examples

Alt text

If APPLET is used, provide a text equivalent with the "alt" and "title" attributes and in the content in the APPLET element. This enables the content to transform gracefully for those user agents that only support one of the two mechanisms ("alt" or content).

  • <applet code="Press.class" width="500" height="500" alt="Java applet: how temperature affects pressure.">
    • As temperature increases, the molecules in the balloon...
  • </applet>

When embedded into web pages, few plug-ins are currently directly accessible. Some of them (e.g. RealPlayer) are more accessible as standalone products. It may be better to invoke the whole program rather than embed movies into pages at this point.

Suggestions for testing this on your pages

  • Opera with Java and Javascript turned off
  • Lynx text-only browser
  • Pass/Fail Examples
[Back To List]