Scripts, Events, & Plug-Ins/PDF, Web Accessibility, The University of Arizona

Requirement:

Provide contact information so that users can ask questions or request the information in an alternative format.

When embedded into web pages, few plug-ins are currently directly accessible. For each script or plug-in, provide a way for the viewer to contact you so that they request the information in a different format or ask questions about the content or functionality.

PDF Files
Adobe's Portable Document Format (PDF) is a popular method to place documents on the web that must retain their formatting. Unfortunately, PDFs, depending on how you create them, may not be accessible. Acrobat Reader 5.0 allows screen readers to access PDF documents. However, not all users have this version installed, and not all PDF documents are text-based (some are scanned in as graphics), which renders them useless to many assistive technologies. It is recommended that an accessible HTML version be made available as an alternative to PDF.

When you scan an article and convert it to PDF, you are taking an image of that page. The letters on the page are merely pictures of letters, not actual ascii based text. This makes it extremely hard for readers to see the text; most think a pdf is just another image.

It is perfectly acceptable to include a PDF in your site as long as you also include a text only alternative of the information. For more information on making PDF accessible, see:
- Access.Adobe.com
Power Point
PowerPoint files are currently not directly accessible unless the user has a full version of the PowerPoint program on the client computer (and not just the PowerPoint viewer). It is recommended that an accessible HTML version be provided as well. See:
- How to Create Accessible PowerPoint Slides on the Web
Events

At this time, many elements of Dynamic HTML, such as Javascript, cannot be made directly accessible to assistive technologies and keyboards, especially when the onMouseover command is used. If an onMouseover (or similar) element does not contain any important information (e.g. the script causes a button to "glow"), then there is no consequence for accessibility. If this scripted event reveals important information, then a keyboard-accessible alternative is required or text alternative.

Drop Down/Jump Menus:
For a Drop Down/Jump menu to be accessible, there should be a 'GO' button by the list menu, meaning that the list is keyboard scrollable using the tab key and the arrow keys. The user can then tab to the 'Go' button when the desired link has been selected.
```
	<form name="jump">
	<select name="menu">
	<option value="/">Web Resources Homepage</option>
	<option value="/training/training2.shtml">Training & Tutorials</option>
	<option value="/enable">Accessibility Implementation Plan</option>
	</select>

	<input type="button" onClick="location=document.jump.menu.options
	[document.jump.menu.selectedIndex].value;" value="GO">
	</form> 
```
Without 'GO' button:

Without the 'GO' button, the first link in the list is selected and the browser jumps to this link when the user attempts to scroll the list with the keyboard. This feature is difficult for individuals using Assistive Technologies and / or a keyboard to navigate the information.

Scripts, Events, & Plug-Ins/PDF

Requirement:

Events

Without 'GO' button: