|
Ed-Resources.Net
Universal Access
|
Home | Universal Access
Cultural organizations have embraced the web. The ability to reach traditional audiences as well as new audiences in a cost effect manner has lead to a rapid proliferation of museum web sites. However, although many of these sites are visually striking, in most cases, the beauty is only skin deep.
There is art in the design of a web site. A site that is accessible to all people has a richer meaning and a deeper beauty because it is able to reach more people in more ways.
What is Universal Access? Access to all audiences, regardless of physical disabilities or technological limitations.
Why should museums embrace Universal Access? To reach as many audiences as possible. Because it's the right thing to do. Because it's the law. (see information on the Federal Government's Section 508 requirements)
Cultural organizations are generally dedicated to making their information available to all audiences, including those with disabilities. However, most museum web sites are not easy to navigate or use by the hearing- and visually-disabled. This presentation will cover not only the basics of good web site design, but will include a demonstration of technologies that allow the museum professional to create web sites that can really be used by all.
Visual Impairments
People with visual impairments range from the totally blind to people who have some difficulty reading small print. Visually-impaired users can best be accommodated by supplying alternate text for all images and graphics, ensuring that navigational icons are large and easy to distinguish, and page layouts are flexible. Some visually-impaired users may need to set the default font size in their browser to a larger value. If a page is laid out using tables with fixed sizes, information can be "lost" beyond the borders of the tables or can "disappear" behind illustrations. Select this text, to see an example.
Some people are color blind. For example, 1 out of every 10 males has some trouble seeing color. Green text on a red background can not be distinguished by some people.
Cascading style sheets allow the web designer to control the layout of many different pages using a single "style sheet." Although the current implementation of style sheets is poor and interpretation by different browsers is inconsistent, they promise to make access by visually-impaired users easier. In the future, visually-impaired users may be able to "turn off" style sheets so that the content can be accessed unhindered by complex graphic design.
The use of embedded text is an especially large problem. Embedded text is text that has been incorporated into an image. Unless alternate text is provided, the information in the text is lost to visually-impaired users, to people using text or auditory browsers, and to people using low bandwidth connections to the Internet that have graphics "turned off". Just as important, the text is not available to software programs that index content for web search engines. This results in fewer people "finding" the web site when performing a search. The following examples are provided to illustrate the difficulties visually-impaired users encounter when navigating museum web sites. These sites were sampled in March of 2000.
Hearing Impairments
Hearing-impaired people may be completely deaf, or may have partial loss of hearing. For example, some hearing-impaired users can not distinguish between sounds in the "foreground" and sounds in the "distance". These people may have trouble distinguishing the sounds coming from a computer kiosk and the sounds created by museum visitors walking past. Hearing-impaired individuals are best accommodated by providing graphical or textual alternatives to sound tracks. Mainstream visitors will benefit as well. Text tracks in on-line video can be searched, providing all users with a means to access specific information without having to listen to the entire feature.
Diminished Mobility
Some people suffer from decreased mobility. This can range from stiffness of fingers due to arthritis to complete paralysis below the neck. Many people with disabilities use adaptive technology, software or hardware that is designed to provide easier access to electronic resources. Designing web sites for such a wide range of people is difficult, however, if web site designers adhere to the basic principles of Accessible Design then the developers of adaptive technologies will create tools to assist this population.
Cognitive Disabilities
People with cognitive disabilities may have trouble reading. To better serve this population, web designers should avoid lengthy, text only pages. Navigation of pages should be clear and simple.
Ensuring that a Site is Accessible
- Edit the web site for spelling and grammatical errors.
- Have others inspect the site for clarity and navigation.
- Inspect the Web site with a variety of older and newer graphical browsers.
- Check the Web site with an HTML, XML or CSS validator.
- Inspect the site using alternative browsers that are text or sound based. Select this link to view the current WC3 page that describes some of the available alternative browsers or select this link to view an archived copy of this page (March, 2001).
- Invite impaired users to inspect the site.
General Accessible Design Principles
- Use a simple design. Use simple language. Have the site edited by a professional and have people unconnected with the project review the web site. Remove any ambiguities.
- Provide simple and consistent navigational elements. If you use frames, make sure that any navigation that is provided on one frame is also available on the page linked to from that page. This principle also helps users that "discover" the frame out of context when using a search engine.
- Provide the site with a consistent "look." Use style sheets where ever possible to control the layout and look of the pages. Style sheets can be "turned off" allowing users to directly access the information in the page.
- Keep the layout flexible. Avoid using fixed sizes for tables. Avoid using tables to layout graphics - tables are for tabular data and were not intended to be used to layout graphics.
- Provide high contrast. Avoid the use of background colors and images. Avoid light colored text on dark backgrounds (most printers will not print the background - this results in low contrast documents when printed).
- Use headers to indicate headings. Do not use header tags as a short cut to format text. Headers should be used to organize and outline the content of the page. Improper use may result in confusion.
- Always provide text alternatives to media that may not be accessible to all populations. Avoid using "white" graphics as spacers in web pages. If "white" graphics or "spacer" graphics are used, use alternate text to explain them.
Checklist for Accessibility
- Include short and simple descriptive alternative text (ALT) attributes for all images.
- If the image needs a longer description, provide a link to a detailed description of the image. Do this by either using the LONGDESC attribute or place a "D" linked to the longer description, next to the image.
- Avoid image maps. If a graphical interfaces is desired, consider "chopping" the main graphic into separate units and provide one link from each unit. This avoids problems with backward compatibility and eases problems for the visually-impaired. When imagemaps are used, always provide text alternatives.
- Make text links descriptive so they make sense when read out of context.
- Keep links to one per line or separate each link with a non-link character or a graphic image.
- If using graphical links, consider providing alternative text links as well.
- When using frames, provide alternative non-frame pages as well. This is easily done using the NONFRAMES tag within the page that specifies multiple pages. Framed pages are often pulled up out of context during searches, so be sure to provide basic navigation and titles on each page in the frame set.
- Provide transcripts of audio presentations.
- Provide text equivalents for video clips, either captions that synchronize with the video, or as links to separate pages for transcripts.
- If video images are crucial for understanding the content, provide descriptive video.
- Avoid using tables and columns. Use relative sizes (%) for tables rather than fixed sizes.
- Use HTML or ASCII for file distribution. If you use PDFs for distribution of formatted materials, provide a link to access.adobe.com and check that the PDF converts well to HTML or ASCII before posting on the web site.
- Outline page content as much as possible. Use appropriate HTML based headers (e.g. H3) and lists, both ordered and unordered.
Resources
- W3C Web Accessibility Initiative
The W3C provides the most up-to-date information and is the best place to start when research web accessibility issues. - References on Web Accessibility
These resources have been extracted from the W3C Web Accessibility Initiative web site and are provided here as a courtesy. This information was last updated 15 February 2001 by Sally De Angelis, Judy Brewer. Copyright © 1997 - 2001 W3C (MIT, INRIA, Keio ), All Rights Reserved.). Please visit the W3C Web Accessibility Initiative web pages for the most up-to-date listing.
- WAI Resources
Key Web accessibility resources at W3C.
- Mainstream Developers - Accessibility Information
Links to accessibility information at mainstream Web software developers.
- Projects, Research, Resources
Assorted links to projects, research, resources related to Web accessibility at other organizations. Please note separate list of links to legal, policy, and governmental Web sites relating to Web accessibility. (Additional information welcome.)
- Adaptive Technology Resource Centre, University of Toronto
- The Archimedes Project, Stanford University
- Aware Center, HTML Writers Guild
- Bartimeus Educational Institute, The Netherlands, Accessibility.nl
- Center for Applied Special Technology (CAST)
- Do-It Program, University of Washington
- National Center for Accessible Media (NCAM), WGBH
- Optavia
- PASIG (Portuguese Accessibility Special Interest Group)
- Project MATHS (Mathematical Access for Technology and Science for Visually Disabled Users)
- Project HIIT: Internet for the Hearing Impaired
- Royal National Institute for the Blind's Accessing Technology fact sheet
- Science Access Project
- Starling Access Services
- TEDIS (Technological Enabling of Disabled and Older People, GMD
- Trace Research and Development Center, University of Wisconsin, Madison
- Videncenter for Synshandicap, Denmark
- WebABLE!
- Web 3D Consortium
- Papers, Articles
Also see Policies Relating to Web Accessibility which includes some policy papers.
- Disabled Accessibility, the Pragmatic Approach, by Jakob Nielsen
- Nomadicity, Disability Access, and the Every-Citizen Interface, by Dr. Gregg Vanderheiden, Trace R&D Center
- People with Disabilities and NII: Breaking Down Barriers, Building Choice, by Susan Brummel, CITA
- Universal Access to the National Information Infrastructure (NII), by Dr. Gregg Vanderheiden, Trace R&D Center
- Tips Provided by Cynthia Waddell, ADA Coordinator, San Jose, CA (2000)
- Reasons to Apply Principals of Universal Design
Much of this information is provided by Kristin Johnson.
- Web Site Validation Services
- Access Adobe
Adobe provides a service to translate PDF documents to standard HTML or ASCII formats which can be read by screen readers. Select this text to learn more about Adobe Access.
All materials © Jim Angus, 2000. I would like to thank Kristin Johnson for providing me with a copy of her paper, Developing An Accessible Museum Web Site, December 20, 1999, Thesis Document, Cooperstown Graduate Program in Museum Studies. It has been invaluable in helping me prepare this web site. Select this text to view the MW2001 outline.