Scripts - Checkpoint (l)
The law states:
"When web 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."
You should generally stay away from using scripts (most notably JavaScript) to generate important content. If you decide to do so, the content generated by the scripting should be accessible. For example, the content must be available using keyboard only navigation.
A more stringent requirement is to turn off JavaScript in your browser, and see if your web site retains its core meaning and navigational elements.
The Cal Poly Site with Scripting Turned Off
If you turn off scripting on the Cal Poly web site, a few features do not work. None of these features is essential to the web site though. The pictures of Poly Reps in various areas of Cal Poly no longer change each time you open the web page. The "Information for" links are now aesthetically static. The quick links menu also does not work, but the links in the menu can be followed through other means. Most of the functionality is still intact, however.
You should also never use JavaScript to automatically direct users to a web site. Web site designers use this technique often with pull-down lists containing quick links. Screen readers cannot automatically read the text within the pull-down menu, and users cannot use the arrows to go up and down the list, since it will take them to the selected web site. The Cal Poly web site currently uses this technique. When scripting is turned off, these quick links no longer work. If the web site required the user to click on a Go button before being directed, the quick links would be accessible.
You can see an example of this at ESPN's basketball home page. Use the keyboard to navigate through the pull-down menu of NBA teams on the left side of the web site. Try highlighting and reading through each team using the down arrow. You will find that every time you highlight a new team, you will be automatically directed to the team's web site. Disabled users wanting to go to a team lower in the menu would have to go through all the other teams' web sites above to get to the one they actually want. To fix this, you should always provide a button (most commonly labeled "Go") for users to click on to go to a web site selected from a pull-down menu.
Helpful Web Sites