Applets

Java, unlike JavaScript, is not a scripting language. Rather, it is an application programming language that was developed by Sun Microsystems. It deserves special mention in this scripting section because Java applets are typically used to design Web-based user interfaces for forms, animations, simulations, transactions, calculations and more.

Much of the information for JavaScript presented in this section also applies to Java applets, for example: choosing device-independent actions, triggering events with active input from users, ensuring accessible form validation, and ensuring that the content is accessible using a keyboard. Obviously, though, the coding techniques are entirely different.

Because a Java applet is a stand-alone program, it is subject to Section 508 guidelines for software applications and operating systems in addition to the guidelines for Web-based intranet and internet information and applications. Application developers must ensure that they are familiar with these guidelines, and that they implement industry best practices.

Java applets should be used only when more accessible methods of presenting the content are not sufficient. For example, if the same function can be realized using a standard Web input form, then the non-plug-in option should be chosen.

REQUIRED:

When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with §1194.21(a) through (l). [Section 508, Part 1194.22, Paragraph (m)]

Note: Applets can be used to design complete applications that have their own user interfaces. Therefore, applets must also conform to the Section 508 regulations outlined in § 1194.21 for software applications and operating systems.

When electronic forms are designed to be completed on-line, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues. [Section 508, Part 1194.22, Paragraph (n)]

Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported. If this is not possible, provide equivalent information on an alternative accessible page. [W3C WCAG 1.0, Checkpoint 6.3, Priority 1]

Ensure that any element that has its own interface can be operated in a device-independent manner. [W3C WCAG 1.0, Checkpoint 9.2, Priority 2]

For scripts and applets, ensure that event handlers are input device-independent. [W3C WCAG 1.0, Checkpoint 6.4, Priority 2]

Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies. [W3C WCAG 1.0, Checkpoint 8.1, Priority 2]

EXAMPLE:

If you provide any material on a Web site that requires software over and above a basic Web browser, it is your responsibility to:

1. Give users a link to download the additional software, and
   
   
2. Ensure that any application or plug-in you link to is, itself, compliant with Section 508 requirements for software.

Always ensure that the interface for your applet can be accessed using a keyboard. This includes providing keyboard input focus, a proper tab order, labels, and a logical layout for all components. Provide text alternatives for all icons and graphics. Ensure that the user has control over effects, alerts and timed responses. Do not use color as the sole means for conveying information. And, ensure that multimedia elements are accessible by providing synchronized text captioning and/or descriptive text, depending on the content of the element.

Specific industry-standard coding techniques are available. Please visit the related links below for details.