NOTE: Because your web browser does not support web standards, you will only be able to view the content in a linearized format. To use this site to it's fullest, you may wish to upgrade to a browser that supports web standards.

Additional Resources

Writing directly accessible applets - WAI recommended technique.

Guidelines on accessibility features provided in Java - Sun guidelines

View WAI checkpoint 9.2 - Ensure that any element that has its own interface can be operated in a device-independent manner.

View WAI checkpoint 9.3 - For scripts, specify logical event handlers rather than device-dependent event handlers.

View WAI checkpoint 8.1 - Make programmatic elements such as scripts and applets directly accessible or compatible with assistive technologies.

Priority 1 Item 11
Make scripts and applets that allow users to interpret or access page content, or any other element that has its own interface, compatible with assistive technologies, and ensure that event handlers are input device-independent.

The proper HTML
<p align="center"> <a href="#"
onmouseover="document.the_image2.src='../images/corky.jpg';"
onfocus="document.the_image2.src='../images/corky.jpg';"
onmouseout="document.the_image2.src='../images/spacer.gif';"
onblur="document.the_image2.src='../images/spacer.gif';">Number One</a> ||
<a href="#"
onmouseover="document.the_image2.src='../images/corky2.jpg';"
onfocus="document.the_image2.src='../images/corky2.jpg';"
onmouseout="document.the_image2.src='../images/spacer.gif';"
onblur="document.the_image2.src='../images/spacer.gif';">Number Two</a> </p>

<p align="center"> <img src="../images/spacer.gif" width="106" height="150" alt="Graphics of Corky"
name="the_image2" id="the_image2" /></p>

Why input device-independent?
Interfaces which do not provide flexibility in the type of device used to interact with them are inherently inaccessible. A laptop user may choose to work without a mouse. If this were the case and interactive features on a site required "drag and drop" interactivity as the only means of interaction, the site would be unusable. Similarly, a site delivered through a kiosk or public access terminal with only a touch screen interface would be unusable.

Developing device independent interfaces facilitates porting the site to the widest range of computing devices, including mobile handsets, PCs, and Interactive Voice Response systems (IVRs).

Screen reader users rely entirely on keyboard input and audio output for interacting with websites. Failing to provide support for audio output or the keyboard as an input device will make the site unusable for them. Other users may use voice input for hands-free operation in a busy office, or if they have dexterity limitations.