Login  |  Register          Free Newsletter Subscription
Subscribe to LJ Magazine
Email
Print
Reprint
Learn RSS

A New Age of Accessibility

Laura Hudson explains federal standards that libraries can use to make web sites available to all

by Laura Hudson (netConnect) -- netConnect, 1/1/2002

Library webmasters have struggled to make sites more user-friendly for the disabled since first learning how to use an 'alt' tag. However, conflicting demands have made it difficult to maintain accessibility.

A new set of federal standards may help.

These standards, called Section 508 guidelines, may be a blessing in disguise for those with sites in need of an accessibility overhaul. Not only do the new federal government standards outline a clear blueprint for creating more user-friendly sites, but they can also help you argue for resources, create good policy, and set guiding principles as you move forward with new technologies.

Section 508 falls under the Rehabilitation Act of 1973, which requires that federal agencies make adjustments for those with visual, audio, mobility, and cognitive impairments, including those who are prone to seizures. The 1998 law specifically applies to electronic information technology. Its main purpose is to create governmentwide accessibility standards for anyone who uses the web or owns software, desktop computers, video and telecommunications products, and other information technology.

Link List

  • Access Board
    www.access-board.gov
    This is the federal agency responsible for developing and enforcing accessibility requirements. It wrote the Section 508 standards and offers a lot of information.
  • Accessible Webpage Design:
    Resources
    library.uwsp.edu/aschmetz/
    Accessible/pub_resources.htm

    This site by Axel Schmetzke, University of Wisconsin-Stevens Point Library, is a huge collection of information about web site accessibility, including links to organizations, lists of good and bad examples, policy statements, legal information, discussion groups, tools, workshops, and more.
  • Bobby
    www.cast.org/bobby
    A popular tool from the Center for Applied Special Technology (CAST), this will check your site for common accessibility errors. Bobby checks for Section 508 standards except m, n, o, and p.
  • A List Apart
    www.alistapart.com/stories
    /indexAccessibility.html

    A collection of articles on accessibility from an online zine for web developers of all types. The articles are provocative and useful.
  • Section 508 Homepage
    www.section508.gov
    This site includes the guidelines, information about training and programs, and links to more resources.
  • Techniques and Tools
    for Web Accessibility
    www.csusm.edu/accessibility
    /508_guide_edited.htm

    Created by Adra Hallford, a web designer at Cal State San Marcos, this site shows you step by step how to apply the Section 508 standards, and it provides links to resources for creating accessible multimedia presentations, etc.
  • World Wide Web Consortium's
    Web Accessibility Initiative
    www.w3c.org/WAI
    'WAI, in coordination with organizations around the world, pursues accessibility of the web through five primary areas of work: technology, guidelines, tools, education and outreach, and research and development.' This is an especially useful place to find HTML techniques.
Many kinds of disabilities

How do we create web sites that adhere to Section 508 standards? Keep in mind that small, incremental changes can make a big difference. If, for example, you apply two of the standards to your site each month, you'll have a compliant site in less than a year. You can also focus on fixing the most-used portion of your pages in the first three months, and then work your way through the rest of the site. Most importantly, follow the standards when starting any new pages or web projects.

Since the web is a visual medium, accessibility discussions tend to focus around the visually impaired. But there are many disabilities to consider when designing your site:

Blindness or low vision: These users should be able to read text, not just images, image maps, and tables. Make sure your layout isn't destroyed if the text is enlarged. Maintain contrast, avoid colors as cues for those with color blindness, and don't use frames.

Hearing disabilities: Text-based web sites work well for the deaf or hard of hearing. There is a trend toward using streaming audio and video or interactive applications with sound features that can cause problems for people with hearing disabilities.

Mobility impairments: These users may need devices other than a mouse or a keyboard to surf the web. Some may speak to the computer, while others may use an eye-tracking device combined with a straw in which one can blow to simulate a mouse click or keyboard stroke.

Cognitive impairments: Trouble reading and typing are common but relatively invisible disabilities, and many will need extra time for these tasks. Those with difficulty processing large chunks of text fare better with bulleted lists, graphic illustrations, and short, easy-to-scan paragraphs with large, clear headers. Avoid confusing or poorly presented information.

Seizure disorders: Some flickering images are known to cause seizures.

The good news is that the Section 508 standards are easy to apply if you keep your web site simple. The bad news is that webmasters may have a hard time making their sites Section 508 compliant owing to increasing demand for multimedia presentations, interactive applications, and other complex web projects. HTML was written to present text, and multimedia applications or professional web layout requires advanced skills, especially when accessibility is imperative.

One helpful approach is to educate people about these concerns by holding small workshops, sending e-mail, or raising the issue at relevant meetings. Librarians may get excited about flash animation, and university faculty may get worked up over live streaming video, but it is important to remind people to consider the implications for the disabled.

Utility vs. graphic design

Some of the demand for fancier, more interactive web sites stems from an underlying philosophical disagreement among webmasters, a rift between those who view the web as a huge but chaotic database of information that needs to be whipped into order and those who see the web as a fledgling multimedia presentation platform.

It's my opinion that information-rich web sites like those created by libraries must err on the side of usability and that presentation does enhance comprehension and learning. In fact, in the case of cognitive disabilities, it may even improve accessibility.

Understanding these disparate ways of viewing the web can help us balance demands. For instance, if library staff want to create a web-based PowerPoint presentation with multimedia components, you'll be qualified to articulate reasons why the presentation needs to be made accessible while also being sensitive as to why they are eager to provide information in a more interesting format than pure text.

There are five key points to convey during such a discussion: 1) according to the Census Bureau, 20 percent of users ages 15 to 64 have some kind of disability; 2) many accessibility guidelines are also good design rules that benefit everyone; 3) unequal access to information for those with disabilities is a civil rights violation; 4) a lawsuit can ensue from failing to provide equal access; and, most importantly 5) librarians have always fought for equal public access to information.

There's a lot you can do to create great accessible web sites for everyone. The standards given to us by Section 508 offer a clear way of providing information for all of our users equally.

Conflicting interpretation

Section 508 standards are not the first set of guidelines for web site accessibility. The most well known are those written by the World Wide Web Consortium's Web Accessibility Initiative (WAI). What Section 508 adds to the WAI guidelines is a clear, concise, and codified set of standards and a commitment by the federal government to not only comply with these standards but require that vendors do so as well.

The rules apply to federal agencies but may also include public or university libraries that receive state funding. Two major grant programs-the Technology-Related Assistance for Individuals with Disabilities Act of 1988 (Tech Act) and the Assistive Technology Act of 1998 (AT Act)-require compliance with Section 508.

However, there are conflicting interpretations of the law. The legal counsel for the California Community Colleges Chancellor's Office (CCCCO) and the California State University Chancellor's Office believes that 'without Congressional legislation, the Department of Education lacks authority to compel states to comply with section 508' (www.csus.edu/web/accessibility/CSU_508_memo.htm). On the other hand, the CCCCO states, 'These regulations are applicable to the states by virtue of the Assistive Technology Act of 1998 memo (www.elearn.mtsac.edu/olsc/accessability/508%20Chancellors%20Office.pdf).

No one seems to know whether Section 508 applies to the states, and no one will know definitively until there is case law-which may not happen for years because many such cases are settled out of court. Nevertheless, since universities and public libraries can be sued under the Americans with Disabilities Act, conformity with Section 508 standards for web sites demonstrates our effort to serve all of our patrons equally.


Author Information
Laura Hudson is Electronic Systems and Services Librarian, San Diego State University

 

Enabling Section 508 Standards

Below is an outline of the 1194.22 standards with some mostly nontechnical annotations intended to help those involved with web site planning and development. Refer to the guides referenced in the 'link list' for HTML techniques to apply these standards.

(a) A text equivalent for every nontext element shall be provided (e.g., via 'alt,' 'longdesc,' or in element content).
Images are the most common kind of nontext elements on web sites, but there are others, like sound, that are becoming more commonplace. It is important to consider carefully what constitutes an equivalent meaning. For instance, in Figure 1, the image indicating a link to 'recipe books' should, perhaps, have a longer description that captures the meaning of the image such as 'link to a list of recipe books.' Conversely, a person using voice recognition software instead of a keyboard will have a hard time activating an image link if the labels are not consistent, simple, and clear.

(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.
Equivalence is an issue here, as well. Pure transcription doesn't necessarily capture the essence of, for instance, a streaming video lecture: What if the lecturer writes something on the blackboard? Or begins to yell?

(c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.
Some web forms indicate required fields by marking them with red text, a problem that is easily corrected.

(d) Documents shall be organized so they are readable without requiring an associated style sheet.
This is a good idea anyway because some people turn off style sheets or use old browsers. Disabled users may have their own style sheets set up to do things like increase the contrast or enlarge the text. Style sheets are the most problematic when used for layout, compared with style elements such as fonts and colors. Figures 2 and 3 show an example of a layout that doesn't allow for text to be enlarged.

(e) Redundant text links shall be provided for each active region of a server-side image map.

(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.
These rules exist so that screen readers will be able to read the page out loud. Client-side image maps can (and must) use 'alt' tags, while server-side image maps cannot.

(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.
Screen readers will try to read tables from left to right, then go to the next line and start again unless there is code to indicate otherwise. This may render the data confusing or useless.

(i) Frames shall be titled with text that facilitates frame identification and navigation.
Frames have accessibility problems for so many reasons. I'd modify this guideline to suggest not using 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.
It's difficult to find an example of what this looks like, since it can cause seizures, but I'm having a hard time imagining why one would need flickering on a web site.

(k) A text-only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part [1194.22] when compliance cannot be accomplished in any other way. The content of the text-only page shall be updated whenever the primary page changes.
In short, 'separate but equal' is not acceptable except under extreme circumstances.

(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 common example of this would be JavaScript rollovers that display information about an element of the page. These are called mouse events, which require the use of 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).
It's always a good idea to limit the number of plug-ins that patrons need to download in order to use your site because download is annoying. This is just one more good reason to do so. Adobe Acrobat (PDF) documents are not necessarily accessible using all versions of the reader software.

(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.
Sometimes web designers use tables to make forms line up neatly. If you do this, make sure that input boxes are easily associated with the text describing the information to be input for a screen reader.

(o) A method shall be provided that permits users to skip repetitive navigation links.
If your web site has navigation links throughout at the top or side, imagine how frustrating it would be to hear those being recited by a screen reader on each page. You can use a transparent gif as a link at the top of the page to allow people to skip the navigation links.

(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.
This is a problem with some forms or interactive sites (e.g., databases) that require users to input data within a certain time limit.

Email
Print
Reprint
Learn RSS

Talkback

We would love your feedback!

Post a comment

» VIEW ALL TALKBACK THREADS

Related Content

Related Content

 

By This Author

There are no other articles written by this author.

Sponsored Links




 
Advertisement
Sponsored Links

More Content

  • Blogs
  • Podcasts
  • Photos

Blogs


Sorry, no blogs are active for this topic.

» VIEW ALL BLOGS RSS

Photos

Advertisements





LJ NEWSLETTERS

Click on a title below to learn more.

LJXPRESS
LJ ACADEMIC NEWSWIRE
LJ REVIEW ALERT
CRÍTICAS
Library DVD Guide
©2008 Reed Business Information, a division of Reed Elsevier Inc. All rights reserved.
Use of this Web site is subject to its Terms of Use | Privacy Policy
Please visit these other Reed Business sites