Canada
NLC HOMESEARCHSITE INDEXCOMMENTSFRANÇAIS
Publications*

Designing for Access to the Web for Blind and Visually Impaired Users

by Anthony Pash
Network Notes #52
ISSN 1201-4338
Information Analysis and Standards
National Library of Canada

February 25, 1998


1. Introduction

For those who have access, the World Wide Web is a powerful resource for education, commerce, social interaction, arts, and entertainment. Unfortunately, not everyone has access to the full range of resources available. Blind and visually impaired users have very limited access. Many barriers limit this group's ability to move through the Web. This paper will discuss the nature of these barriers and present some ways to overcome them.

2. Background

When the Internet was first developed, the standard computer interface was still largely text-based. Blind and visually impaired computer users could easily gain access to the Web's resources using technology, such as screen readers and screen magnifiers (both will be explained in more detail later). The Internet represented a huge step forward for these users as it provided them with access to previously unavailable information. For example, Project Gütenberg provided access to hundreds of literature classics without the problems of finding the works in Braille or hiring someone to read the works to them.

The advent of the graphical user interface (GUI) and the World Wide Web, however, changed the nature of the Internet. The emphasis shifted from the distribution to the presentation of information. This is not to say that content suddenly became unimportant, simply that much more emphasis was placed on the way this information was presented. Today, the Web is a mix of graphics, sound, video, animation and text -- all designed to make sites more appealing to users. For users with good vision, fast connection speeds, and the latest computer hardware and software, the Web has become a much more exciting place. For those without these advantages, gaining access to the content on the World Wide Web has become increasingly difficult.

3. Improving Access

Providing blind and visually impaired users with access to information online is no longer the sole task of the developers of adaptive or assistive technology. These developers continue to be involved, but those who set the standards for distributing information on the Web and those who design the sites that present information must also be included. The following is a brief look at the technology available today and the steps that are being taken by those who set the standards. The focus will be on the steps that Web designers can take to ensure that blind and visually impaired people have access to the information presented.

4. Adaptive or Assistive Technologies

The most commonly used assistive technologies for blind and visually impaired people are screen magnifiers, screen readers, and refreshable Braille pads.

    4.1 Screen Magnifiers

    Screen Magnifiers for computers are relatively simple software programs that can be purchased for approximately $30 US. Demo versions can be downloaded from the Web free of charge. This technology magnifies the text on the screen so that users with poor vision can read text that is otherwise too small. Most of these programs allow users to magnify the text by a factor of 2 to 16 times the original text size.

    4.2 Screen Readers

    Screen Readers read text on computer screens and translate the written text into speech using a voice synthesizer. These devices work well with simple text, but current screen readers stumble over unusual punctuation and text presented in columns. These devices allow blind and visually impaired users to ‘read' up to 400 words per minute of simple text on the Web. They currently range in price from $100 to $600 US. The speech synthesizers must be bought separately for $100 to $1 000 US.

    4.3 Refreshable Braille Pads

    Refreshable Braille pads work in a similar manner to screen readers, except that the text on the screen is translated into Braille rather than speech. The pads are roughly the size of a keyboard and are composed of hundreds of pins that are raised and depressed mechanically. These devices are much more expensive than screen readers (between $8 000 and $15 000 US), but have the advantage of allowing the user to scan full sections of a document easily. Screen readers read the text slowly from left to right, one word at a time. This can be very frustrating for someone who wishes to study a piece of writing carefully.

5. Web Accessibility Initiatives

Standards exist (in North America at least) to ensure that people with disabilities have access to all public buildings and services. It would be illegal to design a public library that did not provide ways for people with physical disabilities to access the library's collection. Many groups feel that similar standards should be in place on the Web. The World Wide Web Consortium (W3C), the Royal National Institute for the Blind (RNIB), disability organizations around the world, and North American and European governments are all involved in setting standards for the accessible design of Web sites. The group with the clearest position is the W3C.

The W3C's stated position is:

All the protocols and languages we issue as recommendations should meet or exceed established accessibility goals. In addition, we will actively encourage the development of Web software and content that is accessible to people with most disabilities.

(http://www.w3.org/WAI/Activity.html)

The W3C also has a list of requirements that must be met by everyone involved:

  • Web technologies must allow the creation of accessible end-user products.

  • Technology alone is not sufficient to ensure access: it requires clear guidelines for the use of the technology to ensure access to the widest possible audience. Since Web technology evolves rapidly, a mechanism for keeping the guidelines current must be in place.

  • The guidelines must be clearly understood, adopted, and supported. This requires educational activities as well as tools to measure the level of accessibility of Web content.

    (http://www.w3.org/WAI/Activity.html)

    This is one of a number of initiatives still in the development phase, but it is hoped that they will have a positive impact on the accessibility of the Web.

    6. Designing an Accessible Web Site

    It is not necessary to forsake creativity, innovation, and aesthetics in Web design to ensure accessibility. It is quite possible to design the site you want, while still enabling everyone to have access to its content. The key to accessible design is providing alternative formats. A site designed to take full advantage of the latest HTML tags, multi-media software, and browser plug-ins, must provide alternative pages that are accessible to everyone. These alternative pages must be announced in a prominent position on your site's home page to make them obvious to blind and visually impaired users. There are some very simple rules of alternative-page design.

    The fully accessible web page should:

  • not use tables, frames, bitmapped text, graphics, audio, video, animation, Java, forms, alternate text formats (such as Adobe Acrobat's .pdf), or browser plug-ins (such as Shockwave)

  • use heading tags (H1, H2, etc..) for varied font sizes, rather than specifying fixed font sizes

  • not use tags such as BLINK or Marquee that cause the text to move

  • use <OL>, <UL>, and <LI> tags when presenting lists

  • avoid using uncommon punctuation such as emoticons

  • use font and background colors that are high in contrast (black on white or white on black work best)

  • use descriptive links - links should be able to make sense out-of-context

    If you decide to provide only one format for your site and you find the above restrictions too limiting, there are ways to make your site more exciting, while still providing accessible documents. Below are some general guidelines for creating interesting and accessible web documents.

    General Design Tips

  • As outlined above, any Web document should use heading tags, ordered and unordered list tags, descriptive links, and high contrast colors. Any document should also avoid BLINK and Marquee tags, and uncommon punctuation.

  • If you use tables, make sure that each cell of the table makes sense on its own -- screen readers that are capable of reading tables read each cell separately. If possible, provide an alternate text-only version of the table's contents in a single column.

  • Some screen readers have difficulty identifying the edit boxes in forms, so if you must use them, provide a short description, extra space, or textual cue to alert the user to the location of the edit boxes.

  • Avoid using frames. Frames create a number of challenges for screen readers that are not easily overcome. If you must use frames, please provide an alternate non-frame version.

  • If you use the Adobe Acrobat .pdf document format on your site, you should also provide an obvious link to http://access.adobe.com. This site is maintained by Adobe for the sole purpose of translating .pdf documents on the Web into simple HTML. This is a valuable service that works very well, but it is useless if not readily available.

  • Use alt-text tags for any graphics used in a document. The description given in the text should be very simple. Often, it is easier to describe the function than the appearance of the graphic.

  • Graphical Image Maps should be avoided, but if they are used, a client-side image map with alt-text tags for each of the links should be provided. It is also recommended that a text-only list of links be provided immediately below the map.

  • Blind and visually impaired users generally encounter no problems with audio clips. However, they can create many problems for hearing impaired or technologically challenged users.

  • Video clips are almost completely inaccessible to blind and visually impaired users. If video is used, either a descriptive text transcript or timed, closed captioning should be used in conjunction with the clip.

  • The use of Java causes several problems with accessibility that are too large to go into here. If you have to use Java on your Web documents, you should read a report prepared by the Trace Institute, which details accessibility problems with Java. This document can be accessed at http://trace.wisc.edu/java/report.htm.

  • Test all documents with a variety of browsers and with images turned off.

  • Analyze your pages using "Bobby" (http://www.cast.org/bobby) - a web-based service that scans any HTML document and produces a report outlining its access problems.

    A number of excellent resources on the Web provide much more detailed information for designing accessible Web sites than has been offered here. A list of the best of these sites is included at the end of this document.

    7. Improving Access for the Future

    Designing an accessible Web site today requires careful planning and design, and, often, increased resources. Work to develop new "accessibility-based" standards and technologies will make the task of providing accessible Web pages easier and more straightforward in the future. At present, good design principles can make Web pages accessible and appealing to all users.

    8. World Wide Web Resources


    Copyright. The National Library of Canada. (Revised: 1998-03-17).