L. 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.
Explanation:
Programmatic objects, such as scripts, applets, and other
plugins are not HTML and have their own sets of access issues. It is important
to attend to these issues in order to ensure that the Web page as a whole is
accessible. They can cause a number of different accessibility barriers:
- Blinking text and motion that is gratuitous or that the
user cannot stop can be difficult to read and/or distracting.
- A refresh or redirect of a page may cause the content
to change unexpectedly, when the user is not prepared for it. For example,
the user may be sent to a new page while a screen reader is in the middle of
reading a sentence.
Examples:
Supply "Alt" Tags For Java Applets & Plugins
<applet name="DigiChat"
"codebase="http://rm150nt.cpd.usu.edu/DigiChat/DigiClasses/"
code="digi/digichat/DigiChatApplet.class"
width="200" height="100" align="right"
archive="Client.jar"
alt="This is a chat program which requires a
Java-compatible
Web Browser to run">
<param name="port" value="8303">
<param name="background" value="FFFFFF">
<param name="textcolor" value="000000">
<param name="cabbase" value="Client.cab">
</applet>
Back to
Creating Accessible Web Sites
