Re: Accessible HTML Documents

From: Mark J. Senk WB3CAI (senkmj@ptbma.usbm.gov)
Date: Fri Aug 18 1995 - 05:52:35 PDT


Hi Curtis,
There are solutions to two of the problems you mention about html. HTML
allows for an optional alt tag to be placed on any image. This alt tag
provides a text description for those who use lynx or other character
based browsers. You can see this at http://www.usbm.gov There is a
graphic image of the official seal which depicts a buffalo since we are
part of the dept. of the Interior. You see the words USBM Seal from the
alt tag and others with Netscape can view the image. Hit the backslash
key in lynx to view the source code.
You also say that there should be a limit on the number of links per
line. It certainly is easier when links are placed in lists with one
item per line or when they have a bullet or star beside them.
Occasionally, the "click here" tex makes it obvious what what will
happen. I want to point out that lynx (the browser) has a provision for
numbering hypertext links. Here are my instructions:
1. Press o for lynx options.
2. Press k for keyboard.
3. Press space or another key and you should hear "links are numbered"
4. Press return to accept this and the r key to return to lynx.

You may not see the effect of this change until you open another web
page. Try http://www.yahoo.com which has several links on a link. Now
that they are numbered, you will find it easy to select the one you
want.

The one thing we should all do is to write the designer of the page and
report problems we have or suggest the use of the alt text descriptions
of images. I have heard that the majority ofWWW browsers use character
based browsers and even those who have the graphical browsers often turn
off the display of images for greater speed. I have found most
information providers co-operative.

-- mark

Mark Senk (412) 892-6513 ms5@usbm.gov

On Fri, 18 Aug 1995, Curtis Chong wrote:

> Hello Mike:
>
> Here are my thoughts concerning how web pages (HTML documents)
> should be constructed so as to provide maximum accessibility to
> persons who are blind. Please remember that these are only *MY*
> thoughts. They should not be regarded as representing a general
> consensus within the blind community.
>
> It has been said elsewhere that an HTML document that is composed
> only of text and devoid of all graphical representations provides
> maximum accessibility to the blind person using adaptive technology
> to browse the Web. This is not necessarily true. Even plain text
> can be so constructed as to be incredibly difficult to read with
> screen access technology. In this regard, I refer to the use of
> ordinary text to compose large letters. Since screen access
> technology deals with the screen one line at a time, it is
> difficult if not impossible to understand information using this
> method. So, even if you are using plain text, try to avoid the use
> of large letters comprised of smaller letters. If design
> requirements compel the display of information using this method,
> it is extremely helpful to have the information reproduced below or
> above in plain text.
>
> It is all right to include pictures and other graphical elements in
> an HTML document as long as the picture is described elsewhere in
> the document. It is a good idea to keep such descriptions as close
> to the picture as possible.
>
> Speaking of pictures, although a picture may be worth a thousand
> words, you should not rely solely on the picture to convey
> information. Using a picture alone to pass along an important
> concept rules out understanding by a person who is blind. In
> addition to the picture, use text to convey the concept.
>
> Try to minimize the number of hypertext links that appear on a
> single line. Three is about the most that is convenient. Any more
> than three and the blind person wastes considerable time trying to
> figure out which link on the line is being highlighted.
>
> Absolutely *DO* *NOT* use multi-column newspaper-style text.
> Speech systems read the screen one line at a time, and it is very
> confusing to hear different parts of the document simultaneously.
> Yes, more sophisticated screen readers do allow the user to divide
> the screen up into logical windows, but configuring these windows
> wastes valuable time. The single column format is infinitely
> preferred.
>
> Put as much ASCII text into an HTML document as you can--the more
> the better. Do not, under any circumstances, use bit-mapped images
> of text. Bit-mapped images or "pictures" of text cannot be read by
> any screen access technology for the blind except enlargement
> technology.
>
> Well, that's about all of the accessibility pointers I can supply
> for now. If you have any questions or comments about what I have
> said, please get in touch.
>
> Regards,
>
> Curtis Chong
> curtisc@winternet.com
>
>



This archive was generated by hypermail 2b29 : Sun Dec 02 2012 - 01:30:03 PST