GENERAL COMMENTS

It is possible today to make WWW (HTML) documents that are accessible by simply avoiding the aspects of HTML or WWW browsers which cause the access problems. For example, if you create a document which ONLY has text and hypertext links (no graphics or sounds), then you will have a document which can be accessed by most anyone with a disability using a personal computer that has been adapted for their use. Although this is a rather elementary and restricted use of HTML, it is nonetheless a viable approach, as is using gopher and ftp.

However, a WWW/HTML document does not need to limit itself to text to be accessible. There are a number of strategies that can be used to allow use of graphics and sound while still maintaining accessibility.

- Some of these strategies require changes in either the WWW servers or viewers such as Mosaic.

- Other strategies, however, do not require any changes and can be used today.


Below are some of the strategies from both categories.


Organization of this document

Problems in access to HTML fall into seven basic areas:

  1. In-line graphic elements, pictures, and diagrams;
  2. Separate viewer based graphic elements, pictures, and diagrams;
  3. Audio clips;
  4. Movies;
  5. Image Maps;
  6. Forms;
  7. Tables;
  8. Non-standard page and document formats;
  9. Custom data structures and viewers;
  10. Color.

Each of these is discussed in turn. For each topic, a brief overview of the problem is presented followed by how it should or will be possible to handle the problem in the near future as access features are built into Mosaic, Netscape, W3, etc. This is then followed by things that can be done to make HTML pages available today.
To Table of Contents
To Previous Section - Overview
To Next Section - Quick Reference

Please send comments and suggestions to: web-team@trace.wisc.edu