How should we provide text equivalents for non-text elements on the web?
Note: Please note that this is an archived presentation and content may be out-of-date or incorrect.
Summary
One of the most basic requirements for web accessibility is providing a text equivalent for non-text elements (images, frames, scripts, etc.). Both words in the phrase "text equivalent" are important. In this workshop, learn how to avoid some common mistakes when creating text equivalents.
The presentation covers the following topics:
- What is a "text equivalent"?
- Which page elements require a "text equivalent"?
- Examples of common errors
- Images present the biggest problem
- Eight types of problems with image "alt" attributes
- Examples of each of the eight problems
- Advice on the use of "alt" attributes for images.
Presented by: Dey Alexander
Date: 20 March, 2003
|