TECH TALK, By Billie Peterson, Baylor University

Dear Tech Talk

Recently I participated in a discussion in which I heard that it was mandatory for library Web pages to be accessible by people with disabilities because of the 1990 Americans with Disabilities Act — a library could be sued or fined for having pages that aren’t accessible. Is this mandate for real? How in the world are we going to "retrofit" our library Web pages so they are accessible to those with disabilities, or do we just start all over again from the ground up?

Woebegone, Wearied Webmaster

Dear WWW

The answer to your question is — “it depends”.  This “mandate”, as you describe it, sounds like a couple of issues that have been cobbled together to create a somewhat false impression.

The skinny on the issue of mandated accessible Web pages is that in 1998, Section 508 of the 1973 Workforce Investment Act was revised to require greater accessibility of all electronic and information technology development maintained, procured, or used by the federal government.  This act also affects anyone who does business with the US government.  Currently all US government Web sites are undergoing review and revision.  Changes to make them fully accessible are to be implemented by June 21, 2001.  However the Bush Administration may review the issue and implement a 60-day delay.  Also, a few states have issued accessibility mandates for state government Web pages — mandates at the state level could impact the Web pages of public and state-affiliated libraries.

The Americans With Disabilities Act (ADA) roughly states that for publicly accessible areas, “reasonable accommodations” for disabled individuals must be made.  Up until recently, “publicly accessible areas” were thought to be physical facilities; however legal arguments are being made that the Internet and Web pages can also be considered “publicly accessible areas”, albeit virtual ones.  Currently, there is no national or international “mandate” to make all Web pages universally accessible.  However, in 1997 the World Wide Web Consortium (W3C) created the “Web Accessibility Initiative (WAI)” to promote and achieve Web functionality.  The WAI has produced guidelines and checklists that are considered the definitive Web accessibility resources at this time.   Additionally, it seems clear that there are legal issues on the horizon, and it will behoove libraries and others to review and revise their Web sites in light of accessibility issues — and not just because of possible non-ADA compliance.  Technology continues to evolve; people now access Web pages through different devices, such as PDA’s, cell phones, WebTV, and even through voice-activated computers in automobiles.  Many of the changes made to assist people with visual, aural, or physical disabilities will also benefit those accessing the Internet through these new devices.  The good news is that a decision to support “universal access” to library Web pages doesn’t mean rewriting the library’s Web pages from ground zero.   Nor does it necessarily mean that the library’s Web site loses its visual appeal because of a stripped-down or removed graphical user interfaces.

First, here are some of the most common Web accessibility issues:
 

• Images and image maps that don’t use the “ALT” tag or a  “longdesc” option; also “ALT” tags that are too brief or too  lengthy.
• Tables used to format information displayed on a page.
• Color used in text and graphics, especially if there is poor contrast between the background and  the text color or if red or green colors are used to display information.
• Frames used without the “noframes” option and not properly titled.
• Drop-down Java menus.
• Java scripts used without a “no Java scripts” option.
• Uninformative links when taken out of context,  e.g., “Click  Here”.
• PDF files and forms.
• Audio and video files.
• Fixed font sizes.
• Use of blockquotes and lists to create an  indented look, rather than their designed purpose of setting off quotes or  lists.

• Use the “ALT” attribute with all significant images.
• With insignificant images (a bar or a bullet), use ALT=””, using a null value between the “” so the image is ignored by a text reader.
• Whether image links or text links, make sure the text used  for the link is descriptive, e.g.,  “Link to Home Page” instead of just “Home Page” or “Click Here”.
• Use client-side image maps so the “ALT” attribute can be used.
• Use the <br> tag after information in a table cell.
• Use Cascading Style Sheets to achieve formatting, but  also check the pages with the style sheets turned off.  <http://www.builder.com/Authoring/CSSToday/ss01d.html?tag=st.bl. f072099.more.CSSToday_1d>
• Convert PDF files to HTML files and provide links to both.
• With HTML 4.0 and the latest versions of Internet Explorer and Netscape, the [Tab] key can be used to move between links.  The order of tabbing can be controlled by  using the “TABINDEX” attribute within links.
• Another feature of HTML 4.0 is the “ACCESSKEY”  attribute.  When used within links, it implements a keyboard shortcut using the [ALT] key and another specified key, such as [ALT] [G] as a  shortcut to “Go to the Home Page” link.  Be careful not to override any standard browser keyboard shortcuts.
• Provide text-based alternative pages.
• Make a site map available.
• Provide a text equivalent or summary for audio and video files.

Voluntarily making the library’s Web site more universally accessible opens the library’s doors to a wider population.  In particular, the disabled (an estimated 25% of the total population) are better reached — a group for whom the advances in technology and the advent of the Internet and the World Wide Web has been both a blessing (because of the readily available information in computer format) and a curse (because of accessibility issues).

Take the first step — analyze the library’s Web site for accessibility problems; read the WAI accessibility guidelines and checklists; then prioritize the changes needed to make the library’s Web pages more accessible.  There is a plethora of guidelines, checklists, and tools for Webmasters or Web groups to use in the analysis and revision of Web site accessibility issues, some of which are listed below:

Overviews and General Resources

HTML Writers’ Guild.  “AWARE (Accessible Web Authoring Resources and Education) Center”   <http://aware.hwg.org>

National Center for Accessible Media  <http://ncam.wgbh.org>

United States Access Board.  “Board Issues Standards for Electronic Information Technology”.
    <http://www.access-board.gov/news/508-final.htm>

University of Washington. DO-IT Program: Technology and Universal Design   <http://www.washington.edu/doit/Resources/technology.html>

University of Wisconsin Trace Research & Development Center  <http://www.trace.wisc.edu/world/web>

World Wide Web Consortium (W3C).  “Web Accessibility Initiative (WAI)”.  <http://www.w3.org/WAI>

Guidelines

Bartlett, Kynn.  Six Principles of Accessible Web Design: An Introduction to the WAI Page Author Guidelines  <http://www.hwg.org/resources/accessibility/sixprinciples.html>

City of San Jose World Wide Web Page Disability Access Design Standards      <http://www.ci.san-jose.ca.us/oaacc/disacces.html>

Cowen, Amy.  “Building an Accessible Website”  CNET  Builder.com   <http://www.builder.com/Authoring/Accessibility/>

IBM’s Accessibility Guidelines      <http://www.ibm.com/able/guidelines.htm>

Microsoft Accessible Web Design Guidelines      <http://www.microsoft.com/enable/dev/web>

Montgomery College. “Universal Design, The Americans   with Disabilities Act (ADA) and The World Wide Web Consortium (W3C)”.    <http://www.mc.cc.md.us/Departments/dispsvc/universal_design.html>

Nielsen, Jakob.  “Disabled Accessibility: The   Pragmatic Approach”  <http://www.useit.com/alertbox/990613.html>

State of Connecticut Universal Website Accessibility  Policy - Version 4.0, effective July 26, 2000  <http://www.cmac.state.ct.us/access/policies/accesspolicy40.html>

Universal Web Design: Access Washington Style Guide      <http://www.wa.gov/dis/interactive/styleguide/development/universal.htm>

University of Minnesota.  “Computer Accommodations Program — Guidelines for Accessible Web Page Design”.  <http://cap.umn.edu/WebSiteAccessibility.html>

 World Wide Access: Accessible Web Design      <http://www.washington.edu/doit/Brochures/Technology/universal.design.html>

World Wide Web Consortium (W3C).  “WAI Quick Tips Reference Card”  <http://www.w3.org/WAI/References/QuickTips/>

World Wide Web Consortium (W3C).  “Web Content Accessibility Guidelines 1.0”.   <http://www.w3.org/TR/WCAG10/>

World Wide Web Consortium (W3c).  “Web Content  Accessibility Guidelines 2.0, Working Draft January   2001”.  <http://www.w3.org/TR/2001/WD-WCAG20-20010125/>

Checklists

IBM Java Accessibility Checklist, Version 3.0   January 15, 2001     <http://www-3.ibm.com/able/accessjava.html>

IBM Web Accessibility Checklist - Version 3.0   January 30, 2001    <http://www-3.ibm.com/able/accessweb.html>

Microsoft Checklist for Testing Your Web Pages for Accessibility    <http://www.microsoft.com/enable/dev/web/checklist.htm>

WebAble Section 508 Accessibility Requirements for Web Sites   <http://www.webable.com/library/508_guidelines.html>

World Wide Web Consortium (W3C).  “Checklist of  Checkpoints for Web  Content Accessibility Guidelines 1.0"  <http://www.w3.org/TR/WCAG10/full-checklist.html>

Tools

Adobe PDF to HTML Converter  — Converts PDF files to HTML files   <http://access.adobe.com/simple_form.html>

Center for Applied Special Technology (CAST) Bobby —   Free utility that identifies and repairs significant  disability access barriers using the WAI 3 levels of priority.   <http://www.cast.org/bobby>

JAWS — One of the screen reader software programs  used by the blind, available for 40 minute trials.  <http://www.hj.com/JAWS/JAWS37DemoOp.htm>

Lynx (Windows 95/NT) — Free download of Lynx, a text-based browser.  <http://www.fdisk.com/doslynx/lynxport.htm>

LYNX Viewer Online — This service allows Web authors  to see how Web pages appear when viewed with Lynx.
    <http://www.delorie.com/web/lynxview.html>

Logitran RTF to HTML Converter — Converts RTF files to HTML files.  <http://www.logictran.com/>

Macromedia.  Dreamweaver “Check Page For Accessibility Extension”.  <http://dynamic.macromedia.com/bin/MM/exchange/extension_detail.jsp?BV_SessionIDD=halkjfiegilb_fejchjcfjecli.0&extOid=195842>

NEWMAN Color-Blind Design Evaluation      <http://newmanservices.com/colorblind/default.asp>

OutSpoken — One of the screen reader software  programs used by the blink, available for a 30 day trial.  <http://www.aagi.com/aagi/outspoken_products.asp>

SSB Technologies.  InSight — Proprietary software that identifies Section 508 accessibility problems.  <http://www.ssbtechnologies.com/services_0.php>

SSB Technologies.  InFocus — Proprietary software that fixes Section 508 accessibility problems.   <http://www.ssbtechnologies.com/services_1.php>

Sun Systems.  Java Accessibility API.   <http://java.sun.com/products/jfc/index.html#access>

VisCheck Color Blindness Simulator      <http://www.vischeck.com/showme.shtml>

World Wide Web Consortium (W3C).  “Evaluation, Repair, and Transformation Tools for Web Content   Accessibility” — Links to additional tools that assist in identifying accessibility problems with   Web sites and making pages more accessible and that assist disabled Web users to access Web pages.  <http://www.w3.org/WAI/ER/existingtools.html>

World Wide Web Consortium (W3C).  HTML Tidy — Free  utility that cleans up HTML coding errors and can   help to identify where changes need to be made to make pages more accessible.   <http://www.w3.org/People/Raggett/tidy>

Vendors

Starling Access Services  <http://www.starlingweb.com>

SSB Technologies  <http://www.ssbtechnologies.com>

WebABLE  <http://www.webable.com>

Additional Resources:

Adobe.  “Adobe’s Tips and Tools for Optimizing PDF files  for Accessibility.”  <http://access.adobe.com/>

Accessible Web Authoring Resources and Education Center (AWARE).  “Common Myths About Web Accessibility”.
 <http://aware.hwg.org/why/myths.html>

Casey, Carol.  “Accessibility in the Virtual Library:   Creating Equal Opportunity Web Sites”.  Information  Technology and Libraries  (March 1999): 22-25.

Dukart, James. “Guidelines Make Web Sites More   Accessible”.  Virtual Government (August 1999): VG6,   VG13.

Heid, Jim.  “Create a Barrier-Free Web Site”.    Macworld (August 2000):109-111.  <http://www.macworld.com/2000/08/create/barrier-free.html>

Heid, Jim.  “Designing for Other Impairments”.    Macworld    <http://www.macworld.com/2000/08/create/access.html>

Holzschlag, Molly E.  “Web Accessibility with HTML 4.0”    Web Techniques  (December 1999): 22-25.
   <http://www.webtechniques.com/archives/1999/12/desi/>

Kaye, H. Stephen.  “Computer and Internet Use Among People with Disabilities”.  March 2000.  <http://dsc.ucsf.edu/UCSF/pdf/REPORT13.pdf>

Mates, Barbara.  Adaptive Technology for the Internet:  Making Electronic Resources Accessible to All.    Chicago: American Library Association, 2000.  Note,   especially Chap-ter 2, “Click (W)Here(?)— Basic Document Design” and Chapter 12, “Working in   the Real World”.   <http://www.ala.org/editions/openstacks /insidethecovers/mates/mates_toc.html>

Microsoft.  “Microsoft’s Accessibility Center”.  <http://www.microsoft.com/enable>

New York Institute for Special Education.  “Blindness   Resource Center: Access to the Internet and Web”.  <http://www.nyise.org/access.htm>

Olson, Walter.  “Access Excess”.  Reason (May 2000): 49-51.

Reilly, Rob.  “The Tech Coordinator’s Corner: Is You Web   Site ADA-Compliant?”  Multimedia Schools   (September 2000: 58-59.

Schmetzke, Axel.  Library Hi Tech.  A future issue of   Library Hi Tech will deal with “Accessibility of   Web-Based Information Resources for People with   Disabilities”.  <http://library.uwsp.edu/news/news72.htm>

United States Congress.  “Addition to the Record: House  Judiciary Committee Oversight Hearing on the ‘The   Applicability of the Americans with Disabilities Act   (ADA) to Private Internet sites.’”  <http://www.trace.wisc.edu/docs/ada_internet_hearing>

United States Department of Justice.  “ADA”.   <http://www.usdoj.gov/crt/ada/adahom1.htm>

Waddell, Cynthia.  “Applying the ADA to the Internet: A  Web Accessibility Standard”.  <http://www.rit.edu/~easi/law/weblaw1.htm>

Waddell, Cynthia.  “Electronic Curb-cuts”: The ADA in  Cyberspace.  Human Rights (Winter 2000): 22-24.

Waters, Chrystal.  Universal Web Design.    Indianapolis, IN: New Riders Publishers, 1997.
 
 
 

As always, send questions and comments to:

Snail Mail: Tech Talk Billie Peterson-Lugo Moody Memorial Library P. O. Box 97143 Waco, TX 76798-7143

E-Mail: Billie_Peterson@baylor.edu

LIRT News, June 2001. Volume 23, number 4.
To report problems, please contact the LIRT News Production editor at jronan@ufl.edu

  WELCOME BACK ISSUES