CultureWork A Periodic Broadside* for Arts and Culture Workers

In this issue:

Also: a version for printing out that includes space for your notes and comments when rating a site.

A Tool for Analysis of Web Sites' Accessibility to Users with Disabilities

 Below is a checklist to assist you in creating web pages accessible to the widest possible readership. This checklist has been adapted by Doug Blandy from Vanderheiden, G. C., Chishom, W. A., & Ewers, N. (1996), Design of HTML Pages to Increase their Accessibility to Users with Disabilities <http://www.trace.wisc.edu/text/guidelns/htmlgide/ htmlfull.html> and assignments submitted by Richard Bear and Ann-Marie Bilderback, AAD 451/551 Art and Community Services, Program in Arts and Administration, School of Architecture and Allied Arts, University of Oregon, Eugene, OR, Winter, 1997.

 Text Anchors

• Make text anchors descriptive enough that they make sense when read out of context.

 
• Be sure to place a dividing character between links which occur consecutively. Vertical bars may be used to prevent a list of links from being read as one link by speech software.

• Provide an alternative text description (ALT = "[description of graphic]"). This includes all graphics - even decorative ones. Otherwise, the user with a text-based browser (LYNX, usually) sees a note saying there is a graphic but doesn't know what it is.

 
• Include a text anchor to a page describing the graphic (we recommend a capital "D" or a short phrase located next to the picture) which takes you to a separate page with a full description of significant graphic elements, pictures, etc.

 
• Provide an alternate text-only page which translates all of the graphic and text information into text only. This can provide a fast access method for all users. You may have text-only pages for just troublesome pages or all pages at your site. Users should be able to switch back and forth between text-only and graphic versions of the page.

• Audio clips should include a link to a page with a transcript or description of the sound file .

 
• Movies should include captions or text tracks with a description of the sounds and words in the movie.

 
• Image maps should be complemented by a set of text anchors for all links accessible through the image map.

• Provide forms in a format that can be downloaded, then mailed or emailed back. Phone numbers should be included for additional information.

 
• Tables with multiple cells cannot be read be presently read by speech software and should be avoided entirely (no good solution presently exists).

 
• Make text-only versions available for all pages.

 
• Non-standard data structures and viewers should be avoided.

• Background patterns and color should contrast well with the lettering to maintain readability (background refers to both backgrounds of pages and backgrounds of images).

 
• Select colors that will make your pages easy to read by people with color blindness. One good test is to see if your pages are readable in black and white.

• Always test your pages using a variety of browsers and platforms (PC, MAC, UNIX). Be sure to include text-based browsers (LYNX) and use graphic browsers with images turned off.

CultureWork seeks submissions (500-1500 words), topic ideas, and constructive criticism. Graphics that express the spirit of Community Arts are especially welcome, to be published with attribution. Send to Maria Finison at mfinison@darkwing.uoregon.edu or via snailmail: care of Arts & Administration Program, School of Architecture and Allied Arts, University of Oregon, Eugene Oregon 97403.