Web Team Home

Web Team Charge

Team Membership

Website Mission Statement

Redesign Project
(goals | timeline)

Meeting Minutes

Comments/Suggestions

Pagemaster's corner TOC:

Style Sheet

Server Side Includes

Templates

Standards

Prodecures

Quality Assurance

Section 508 Workshop Handout

Why Build Accessible Web Tools?

  • A good percentage of our patrons have a disability. Our mission statement doesn't say that we're here to "support the teaching, research, and service functions of the University unless you have a disability."
  • Improving your accessibility can improve your usability, too.
    • Palm Pilots
    • Modems at home
  • Federal law and ADA lawsuits

    • Kinds of Disabilities

    Blind/Low Vision
    • May use a screen reader or a Braille printer.
    • May enlarge the size of the text on the page or use Zoomtext to enlarge it.
    • May have trouble seeing low-contrast text.
    Deaf/Hard of Hearing

    Mobility Impairments
    • May not use a mouse
    • May not use a keyboard
    • May speak to the computer
    • May use another input device
    Cognitive Impairments
    • May need extra time for tasks
    • May use a screen reader
    • May have trouble with poorly presented information
    Seizure Disorders
    • Flickering images can cause seizures

    Section 508 Guidelines

    (a) A text equivalent for every non-text element shall be provided (e.g., via "alt", "longdesc", or in element content).
    • What constitutes an equivalent meaning?
    • Eye candy images should use an empty ALT attribute.
    • "D" link can also be used.
    • ALT attributes for images with text in them that are links must match the content of the image so that people who talk to their computer instead of typing know how to activate that link.
    (b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.
    • Just a transcript isn't ok-actions must also be described.
    • Powerpoint can't just be saved as html.
    • Flash and other media are the biggest problems here.
    (c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.

    (d) Documents shall be organized so they are readable without requiring an associated style sheet.
    • Disabled users often set up their own stylesheets.
    • This is a bigger deal when stylesheets are used for layout.
    (e) Redundant text links shall be provided for each active region of a server-side image map.
    • Client-side image maps (image maps that are defined in the HTML) can have ALT attributes for each active area, whereas Server Side image maps cannot.
    (f) Client-side image maps shall be provided instead of server-side image maps except where the regions cannot be defined with an available geometric shape.
    • Generally, server side image maps are more difficult for JAWS software.
    (g) Row and column headers shall be identified for data tables.

    (h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers.

    Here is an example borrowed from the W3C.




    (i) Frames shall be titled with text that facilitates frame identification and navigation.
    • There are so many documented problems with frames that only three people in the world should attempt to use them.
    (j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.

    (k) A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of these standards, when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes.
    • Don't use text-only pages as an excuse to get out of making your site accessible.
    • Text only pages are sometimes redheaded stepchildren.
    • If it's necessary, make it one of the first two links on the page.
    (l) When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by assistive technology.
    • A javascript mouse event can't happen without a mouse!
    (m) When a web page requires that an applet, plug-in or other application be present on the client system to interpret page content, the page must provide a link to a plug-in or applet that complies with §1194.21(a) through (l).
    • That means that you can't link to a necessary plug-in that doesn't comply with these guidelines.
    • PDF's are only accessible on a PC platform with the latest version of Acrobat and the latest version of JAWS.
    (n) When electronic forms are designed to be completed on-line, the form shall allow people using assistive technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.
    • Make sure that input boxes are easily associated with the text describing the information to be inputted.
    • This sometimes is a problem with tables-JAWS doesn't read the text in the correct order.
    (o) A method shall be provided that permits users to skip repetitive navigation links.
    • You can use a transparent gif with an ALT attribute for this.
    (p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.
    • This is mostly a concern for interactive sites.

    Resources

    Adra Hallford's Section 508 Guide
    A comprehensive guide to Section 508 guidelines, with tips and tricks.
    http://www.csusm.edu/accessibility

    Bobbi accessibility checker
    Will check your pages
    http://www.cast.org/bobby/

    Flash Accessibility
    Tricks for making Flash presentations accessible.
    http://www.macromedia.com/software/flash/productinfo/accessibility

    Lynxview
    Use this to emulate how your page would look in a text-based browser (which is a pretty good emulation of how JAWS would read the page).
    http://www.delorie.com/web/lynxview.html

    PowerPoint
    Guide to making PowerPoint presentations accessible.
    http://www.webaim.org/howto/powerpoint

    Screen Reader Simulator
    Simulates using the JAWS software used by visually impaired people.
    http://webaim.org/tutorials/uofa/sim1

    University of Arizona Web Accessibility Resources
    Includes links to testing tools, makeovers and examples, and more.
    http://uaweb.arizona.edu/resources/accessibility.shtml

    VisCheck Simulator
    Makes your page look as it would if you were colorblind.
    http://vischeck.com/vischeckURL.php3

    Web Accessibility Initiative
    Even more intense guidelines than those provided by Section 508.
    http://www.w3.org/WAI/



    Back to the top | Back to the Pagemaster's Corner
    Revised 6/5/02 by Laura Hudson
    Contact: Laura Hudson: lhudson@mail.sdsu.edu