 Standard
12 -- Scripting.
When pages utilize scripting languages to display
content, or to create interface elements, the information provided by the
script shall be identified with functional text that can be read by assistive
technology .
Examples:
12.1 --
Within scripts information is text-based or a text alternative is provided.
12.2
--
All scripts (Javascript, pop-up menus, etc.) work with keyboard-accessible
alternatives (either within or outside of the script) that provide equivalent
functionality.
Scripting -- Do's and Dont's
| Do |
Don't |
Use scripts that create usable elements and/or readable
text in the page. | Use scripts that generate server-side objects or
content that cannot be read when scripts are turned off. |
Why: When authors do not put functional text with a
script, a screen reader will often read the content of the script itself
in a meaningless jumble of numbers and letters. Although this jumble
is text, it cannot be interpreted or used. How: Test pages with browser scripting turned off.
Test page functionality using only the keyboard. Avoid mouseover events
and script embedded images. 
Get more help with scripts, visit Jim
Thatcher's "Scripts and Applets."
 Back
Next
Top
of Page || Return to Index
 View/Print
in PDF format. (Acrobat
Reader required.)
|
