Top of the page

[About accessibility] [Skip UCSF navigation]

UCSF logo

End of UCSF navigation

[Skip breadcrumbs navigation]

UCSF which contains School of Pharmacy which contains Information for Web Developers which contains Web Accessibility

UCSF School of Pharmacy

Web Accessibility

The following information is a presentation outline describing why and how to build Web sites that are more accessible to a wider range of people and devices. The information below is also available in PDF for printing and presentation.

January 2003
Frank Farm, Web & Data Services Manager
UCSF School of Pharmacy

Who needs accessibility?

Hearing

Vision

Mobility

Learning

How many people is this?

It's estimated at 15%.

U.S. population = roughly 290 million people (15% = 43.5 million).

World population = roughly 6 billion people (15% = 900 million).

Are these people part of your audience?

Do men visit your site? About 8% of them are color-blind.

In the U.S., over 19 million adults reported having trouble with vision in a 1997 CDC survey.

In the same survey, over 28.7 million reported "a little trouble" with hearing and over 5.9 million reported "a lot of trouble or deaf."

What is Accessibility?

In real life:

  1. Hearing: closed captioning for films, sign language interpreters for live events
  2. Mobility: ramps, elevators, kneeling busses
  3. Vision: large print books, elevator buttons with braille
  4. Learning: special learning approaches/techniques

On the Web:

  1. Deaf & Hard-of-hearing: visual cues in addition to audio cues, captioning for multimedia (Flash animation, audio, video with sound), amplified headphones (Relevant only when your Web site contains sound.)
  2. Mobility: Navigation, Fitt's Law
  3. Blind: screen readers, dynamic braille printers
  4. Visually-impaired: use browser features to make font sizes larger or use screen magnification tools
  5. Color-blind: use stylesheets to force usable color preferences for text colors and page backgrounds
  6. Learning: Extremely difficult to address properly, even for today's Web experts in the field

Why Accessibility?

The Goal

To provide equivalent access of effective communication to everyone without imposing undue hardship and without fundamentally altering the program or service.

Understanding the Goal

What is "equivalent access"?
Wheelchair access to a building, "equivalent dignity"
What is "effective communication"?
Equally effective as with non-disabled visitors.
What is "undue hardship"?
Company would go bankrupt
What is "fundamentally altering the program or service"?
Elevators in the Leaning Tower of Pisa.

Publicity Reasons

The potential for bad publicity is real.

Legal Reasons

1973: United States Section 504 (Rehabilitation Act)
Bans discrimination based on disability in any program or activity that receives financial assistance from any federal agency
1990: United States Americans with Disabilities Act (ADA)
Extends Section 504 to include places of public accommodation
1998: United States Section 508 (Rehabilitation Act amendments)
Extends Section 504 to include information technology.
2002: California Senate Bill 105
Affirms that United States Section 508 applies to California governmental entities using information technology.

Financial Reasons

Ethical Reasons

Web accessibility is an issue of equal opportunity and discrimination.

Technical Reasons

How do we make accessible Web sites?

Educate People

More Effective
Less Effective

Impose mandates or legislation, then have people defend why they can't or won't change.

Web site sponsors
Web developers

Include Accessibility in Your Budget

Expose Web Developers to Access Tools

Software
Hardware

Test Your Sites With Disabled People

Best Fixes to Implement First

  1. Create valid code.
  2. Use alt tags for all images (except spacer GIF images and other meaningless graphics).
  3. Use "skip navigation" links before all navigation bars.

Recommended Reading

Non-Technical

  1. Introduction to the Screen Reader (movie) (12 MB, Requires Apple QuickTime)
  2. Access: Everybody Wins
  3. Beyond Accessibility: Treating Users with Disabilities as People

Technical

  1. Joe Clark's Answers -- In Valid HTML
  2. Accessibility and Authoring Tools

Non-Technical and Technical

  1. Dive Into Accessibility by Mark Pilgrim

More Information

There are too many other excellent sources to list concisely and representatively. Google is your friend! For example:

Go To: Information for Web Developers

Shortcut to This Page

To reach this page quickly or share it with others, use pharmacy.ucsf.edu/go/access, which redirects to a longer URL.

For printing and presentation

Thumbnail image of Frank's presentationWeb Accessibility Presentation
Frank Farm
January 2003
PDF, 24 pages, 121 KB
Requires Adobe Reader

Other presentations

Thumbnail image of Robin and Aaron's presentationWeb Accessibility and Cascading Style Sheets: A Tutorial
Robin Sease and Aaron Calhoun
June 1999

Related Links

More Information

For more about Web accessibility, see Google Directory: web accessibility.

[Skip section-level navigation]

End of section-level navigation