<h1>Web Accessibility</h1>
<h2>What Does It Mean?</h2>
Associate Professor of Economics
Webmaster, College of Liberal Arts
"Level A"
Quick links on this page:
[ Highlights ]
[ Images and image maps ]
[ Tables ]
[ Frames ]
[ Applets and scripts ]
[ Multimedia ]
[ When all else fails ]
[ Related topics ]
"A Web content developer must satisfy this checkpoint. Otherwise, one or more groups will find it impossible to access information in the document.
Satisfying this checkpoint is a basic requirement for some groups to be able to use Web documents." (Source: "List of Checkpoints for Web Content Accessibility Guidelines 1.0")
Highlights:
- Provide a text equivalent for every non-text element (for example, via "alt", "longdesc",
or in element content). This includes: images, graphical representations of text (including symbols), image map regions, animations (for example, animated images), applets and programmatic objects,
ascii art, frames, scripts, images used as list bullets, spacers, graphical buttons, sounds (played with or without user interaction), stand-alone audio files, audio tracks of video, and video.
- Ensure that all information conveyed with color is also available without color, for example from context or markup.
- Clearly identify changes in the natural language of a document's text and any text equivalents (for example, captions).
- Organize documents so they may be read without style sheets. For example, when an HTML document
is rendered without associated style sheets, it must still be possible to read the document.
- Ensure that equivalents for dynamic content are updated when the dynamic content changes.
- Until user agents allow users to control flickering, avoid causing the screen to flicker.
- Use the clearest and simplest language appropriate for a site's content.
If you use images and image maps:
- Provide redundant text links for each active region of a server-side image map.
- Provide client-side image maps instead of server-side image maps except where the regions cannot be defined with an available geometric shape.
If you use tables:
- For data tables, identify row and column headers.
- For data tables that have two or more logical levels of row or column headers, use markup to associate data cells and header cells.
If you use frames:
- Title each frame to facilitate frame identification and navigation.
If you use applets and scripts:
- Ensure that pages are usable when scripts, applets, or other programmatic objects are turned off or not supported. If this is not possible, provide equivalent information on an alternative accessible page.
If you use multimedia:
- Until user agents can automatically read aloud the text equivalent of a visual track,
provide an auditory description of the important information of the visual track of a multimedia presentation.
- For any time-based multimedia presentation (for example, a movie or animation), synchronize equivalent alternatives (for example, captions or auditory descriptions of the visual track) with the presentation.
And if all else fails:
- If, after best efforts, you cannot create an accessible page, provide a link to an alternative page that uses W3C technologies, is accessible, has equivalent information (or functionality), and is updated as often as the inaccessible (original) page.
Related topics
[ Workshop home ]
[ For Whom? ]
[ Why? ]
[ Overview ]
[ "Levels" ]
[ More information ]
[ Examples ]
[ ]
( Privacy Policy | Last saved August 17, 2004 )