Flylib.com

Books Software

 
 
 

Chapter 5. User Experience: On the Bus

Team-Fly    

Maximum Accessibility: Making Your Web Site More Usable for Everyone
By John M. Slatin,, Sharron Rush
Table of Contents
Part I:  Accessibility and Why It Matters


Chapter 5. User Experience: On the Bus

Getting There Is Half The Fun

Getting Information About Getting Around Town

The Trouble with Tables

User Experience Narrative: Austin's Capital Metro

Other Examples

Problem Solving: Designing a New Bus Schedule


Team-Fly    
Top
 

 
Team-Fly    

Maximum Accessibility: Making Your Web Site More Usable for Everyone
By John M. Slatin,, Sharron Rush
Table of Contents
Chapter 5.  User Experience: On the Bus


Getting There Is Half The Fun

This is the second of our user experience chapters, in which we illustrate the impact of particular design features by inviting you to experience the Web along with us as we browse using assistive technology. In this chapter, we are trying to locate and understand the schedule for a specific bus route in Austin, Texas. You will see that most of the barriers we encounter have to do with the lack of table organization and labeling that could, in fact, make this a fairly straightforward and relatively easy task.

HTML Elements and Attributes Addressed in This Chapter

Elements

<pre>, <table>, <caption>, <thead>, < tbody >, <tr>, <th>, <td>, <form>, <abbr>, <acronym>

Attributes

headers, summary

Accessibility Checkpoints and Standards Addressed in This Chapter

Web Content Accessibility Guidelines 1.0 Checkpoints

3.0. Use markup and style sheets and do so properly.

5.1. For data tables, identify row and column headers. [Priority 1]

5.2. For data tables that have two or more logical levels of row or column headers, use markup to associate data cells and header cells . [Priority 2]

5.5. Provide summaries for tables. [Priority 3]

5.6. Provide abbreviations for header labels. [Priority 3]

11.2. Avoid deprecated features of W3C technologies. [Priority 2]

12.0. Provide context and orientation information.

12.1. Title each frame to facilitate frame identification and navigation. [Priority 1]

13.0. Provide clear navigation mechanisms.

13.4. Use navigation mechanisms in a consistent manner. [Priority 2]

Section 508 Standards, 1194.22

(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.

(i) Frames shall be titled with text that facilitates frame identification and navigation.


Team-Fly    
Top
 

 
Team-Fly    

Maximum Accessibility: Making Your Web Site More Usable for Everyone
By John M. Slatin,, Sharron Rush
Table of Contents
Chapter 5.  User Experience: On the Bus


Getting Information About Getting Around Town

Millions of Americans spend huge amounts of time in their cars every day, driving to and from work, school, shopping centers, doctors ' offices, and the homes of friends and relatives. Many people don't think twice about jumping in the car and driving to the store to pick up an extra quart of milk or a bottle of detergent. Some people climb into their cars when they get angry or upset and just drive around until they calm down. Our entertainers sing about riding around in their automobiles—Chuck Berry, Jan and Dean, the Beach Boys, and Lyle Lovett. Our novelists celebrate it—think of Jack Kerouac's Beat classic, On the Road. And then of course there are the movies— Thelma and Louise, Scent of a Woman, Breathless .

But there are people in the United States who don't drive—not because they don't want to, for the most part, but because they can't. Some can't drive because the nature of their disabilities is such that it makes driving impossible . Others can't drive for economic reasons. Seventy percent of people with disabilities who are willing and able to work are unemployed; over a third of Americans with disabilities have incomes below $15,000 a year. [1] The poverty that so often accompanies disability prevents them from owning cars and makes it difficult for them to access the jobs that might allow them to do so.

[1] Bush Administration. Executive Summary: Fulfilling America's Promise to Americans with Disabilities. Accessed May 22, 2002, at http://www.dol.gov/_sec/programs/ptfead/freedom_init.htm#2.

Twenty-five million Americans with disabilities depend on public transit to get where they need to go—to schools , doctors' offices, stores, friends' houses , places of worship, job interviews, and all the other places that Americans go. The ADA mandates that public transportation be accessible to people with disabilities, and there has been considerable progress since the ADA took effect in 1992. But the situation is still a problem. According to the present Bush Administration:

Transportation can be a particularly difficult barrier to work for Americans with disabilities. In 1997, the Director of Project Action stated that "access to transportation is often the critical factor in obtaining employment for the nation's 25 million transit dependent people with disabilities." Today the lack of adequate transportation remains a primary barrier to work for people with disabilities: one-third of people with disabilities report that inadequate transportation is a significant problem. [2]

[2] Bush Administration. Executive Summary: Fulfilling America's Promise to Americans with Disabilities. Accessed May 22, 2002, at http://www.dol.gov/_sec/programs/ptfead/freedom_init.htm#2.

Which brings us to the topic of this chapter. Part of the challenge of access to public transportation is access to information about public transportation, especially to information about routes and schedules.

Many public transportation systems publish their route and schedule information on the Web. These schedules are usually— though not always, as we'll see—in the form of HTML data tables . The WCAG 1.0 defines data tables as those used to "represent logical relationships among data," in this case the relationships among times and locations. Most of this chapter is concerned with specific examples of the way various public transportation systems use HTML tables to make their schedules available and suggested features that can be incorporated to improve accessibility for users with disabilities.

We'll examine schedules published by Capital Metro in Austin, Texas; by the Long Island Rail Road and New York's Metropolitan Transportation Authority; and by the Santa Clara Valley Transportation Authority in California, along with passing references to other systems. In each case, we'll be interested not just in the tables themselves but also in the larger context in which these tables are used to present information about bus routes and schedules. Ultimately, however, we're not concerned about the tables at all: we're concerned about the quality of the rider 's experience on the Web .

Our only concern as Web developers might be to publish schedule information; by the same token, our riders may be interested in nothing more (or less) than finding out what time a specific bus will reach one specific intersection. We have to remember, though, that each rider is going to have an experience of some sort when she or he comes to our site. Riders will succeed in finding the information they're looking for or they'll fail. If we do our job well, most riders won't even notice what we've done—they'll merely come to the site, get what they need, and go on about their business. In this chapter, then, our aim is to think about the kinds of experiences riders might have as they try to use the bus schedules published on the Web.


Team-Fly    
Top