Description

A text equivalent for every non-text element must be provided.

Scope

This standard applies to scripts. If scripts are not in use, the provision is satisfied.

Explanation

Client-side scripting languages are coded in with the page's content and HTML tags, and are executed by the user agent (i.e., web browser). If necessary, you can check for the presence of a scripting language on a web page by reading through the source code for the <script> tag (e.g. <script src="scriptname.js" language="JavaScript1.2">).

Procedure

Provide a descriptive text equivalent for any script.

Guidelines

Does the script provide text?

In the event that a script might not load onto a user agent (e.g. the user might have deactivated the execution of scripting languages at the browser level), you must ensure that all users can access identical content or data.

Place alternate text inside <noscript></noscript> tags to accommodate those who use older browsers or who have deactivated the execution of scripting languages at the browser level. However, content within <noscript></noscript> tags will not be read by assistive technology if the browser's scripting capabilities are left on (in such a case, the browser will correctly ignore the <noscript></noscript> tags), so a method of providing the content in additional to using <noscript></noscript> tags must be created. In short, all users should be able to access identical content or data.

Any hyperlinks used as an alternate method of accessing content or data should contain the title and alt attributes to provide a meaningful description for those with assistive technology.

Source

1 TAC 206.50(a)(1) • 1 TAC 206.70(a)(1) • Section 508 1194.22(a)

To Learn More

See the W3C Recommendation on Scripts.