Please Note: This section of our website contains information from past work in this area and is largely out of date. The following links include more up-to-date resources on this topic.
- Guidelines for creating accessible scripts.
How does this work?
Control the browser
Interact with the contents of a document
Interact with the user and control the appearance of a document
Information presented in tables cause many problems for users with screen readers (see the Unified Web Accessibility guidelines for more information). HTML 4.0 allows authors to associate meta-information with table cells to help alleviate this problem. However, it will be a while before page authors make extensive use of these element attributes and web browsers can pass this information onto users. In the meantime, we create a script to transform tables into more accessible formats.
Frames can also be a problem. Users with small screens may not see much data other than frame dividers, and some screen readers do not identify each screen as a separate window. Several browsers support the
<NOFRAMES>element, which will load an alternative page that does not use frames (if provided by the author). However, browsers that support frames do not yet allow users to request the
<NOFRAMES>option. This script allows the user to select the
<NOFRAMES>version of a page. This can also be accomplished by placing a link to the
<NOFRAMES>version of the page at the beginning of the main frame. [Example 4] of a page with multiple frames.
Lists of lists can also be difficult to interpret since indentation is often the only clue as to where in the hierarchy an item falls. This example [Example 5].
3. Guidelines for creating accessible scripts
- Trigger events with active input from users rather than nonactive triggers.
An active trigger is a mouse click, selection of an option in a list, or a key press. Nonactive triggers are activated when a page is loaded, after a certain amount of time has expired, or when the mouse passes over an object. Nonactive triggers are useful for highlighting information but should be used carefully and should not greatly alter the contents of the page, unless notification is given to the user.
- Provide a mechanism for the user to freeze or slow-down any moving or blinking objects, particularly those that contain text.
- Provide a
<NOSCRIPT>option for all scripts.
...some Tcl script to show a billboard of sports scores...
<P> To access today's scores <A href="scores.html">visit our text-only version.</A>
- Make scripts and applets keyboard operable (using standard conventions).