W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > January to March 1999

resending article in plain text

From: Robert Neff <rneff@moon.jic.com>
Date: Wed, 31 Mar 1999 20:16:22 -0800
Message-ID: <004001be7bf6$66e1d500$4b109cce@rneff.jic.com>
To: "IG" <w3c-wai-ig@w3.org>
some people request this be sent again in plain text.

http://www.internetworld.com/print/current/webdev/19990329-access.html  I
have inserted the text after the next paragraph.

In hardcopy see page 19 of interent world by James C. Luh.   Title:  Access
for All, Transit site redesign allows browsing by everyone, including
disabled. Feature is Tim Moore, web site manager for BART, Bay area transit

<Start article>

March 29, 1999
Access for All
By James C. Luh

Many sites on the Web aren't shy about recommending or even requiring that
their visitors surf with a particular browser, plug-in, or configuration
option. But such Procrustean policies aren't an option for the San Francisco
Bay Area Rapid Transit District (BART), a public transit system that must
cater to any and all users.

BART recently retrofitted its Web site to make it accessible to a user
population as diverse as BART's ridership, including persons with

"We serve a huge, very diverse online customer base," said BART Web site
manager Tim Moore. "We're constantly working to maximize our reach, and I
view this as another effective way to do that."

Moore said that while researching Web standards, his staff came across what
are now called the Web Content Accessibility Guidelines. The guidelines,
published by the World Wide Web Consortium's Web Accessibility Initiative,
are meant to help Web authors ensure that their sites can be accessed by a
wide variety of users, including users with disabilities, who may be using
unconventional programs, such as screen readers.

For example, the WAI guidelines recommend that images be accompanied by
descriptive text to aid users who are not able to view graphics.

After consulting other resources, Moore concluded that the WAI guidelines
were the best available resource for starting to rework the BART site.

"WAI doesn't seem to make everybody happy," Moore said. "Some people think
it hasn't gone far enough, others think it goes too far, but in my view,
developers need a standard like this as a starting point." State and federal
laws such as the Americans With Disabilities Act require companies and
public agencies to ensure that persons with disabilities can access their
facilities. But government agencies have not yet clearly delineated how
those laws apply specifically to Web accessibility, Moore said. "I've worked
with our legal department to try to determine if there are any established
guidelines in this area," he said, "and there are not." Once funding and
approval for the redesign were in place, Moore said, the BART staff began
evaluating the BART site against the WAI guidelines and making the changes
necessary to bring the site into compliance.

"We were lucky in that the underlying structure appeared to be in pretty
good shape," Moore said. "It wasn't frames-based or too heavily graphic, but
there were a few problems." One of the more serious problems was that the
site did not provide alternate text for use in browsers that do not display
images, Moore said.

Another problem was that the site's navigation bar indicated where a visitor
was in the site by displaying the name of the current section in a lighter
color than the names of the other sections, which could pose a problem for
visually impaired users.

BART has started providing text equivalents for Portable Document Format
(PDF) documents on its site, even though Adobe Systems provides software
resources to help visually impaired users access PDF.

"The indication that I was getting from persons with disabilities who tried
to use that was that it doesn't always represent the copy as accurately or
as precisely as they would like," Moore said.

A serious accessibility problem--and the hardest one to solve--was in an
area that the WAI guidelines do not directly address: The online ticket
purchase feature on the BART site uses Secure Sockets Layer (SSL)
encryption, which some browsers do not support.

"This is a technology issue, more than anything," Moore said. "There are
still people with older browsers or improperly configured browsers." To
accommodate the broadest range of users without compromising their credit
card numbers, the BART site now provides an alternative to the secure
server: A user can submit an order through an unencrypted form, including
only the first five digits of his or her credit card number. The user then
gives BART the rest of the credit card number over the phone.

The secure server issue was especially important to users with disabilities,
said Jean Nandi, a member of the Access BART Coalition, a group formed to
improve access to BART facilities for the elderly, the disabled, and other

"That's particularly sensitive to us," Nandi said, explaining that persons
with disabilities often encounter obstacles buying tickets from other
venues, such as at BART stations.

Nandi said she is glad BART is making an effort to improve its Web site's
accessibility, but in terms of results, she said, the process has seemed
hampered by the same bureaucratic hurdles that often slow progress toward
accessibility in the offline world.

For one thing, she said, Moore's process seemed driven too much by the WAI
guidelines and not enough by dialogue with actual users.

Moore said he recognizes that the guidelines have limitations, and he is
continuing to work with users to address their concerns.

"I'm quickly realizing that just because you implement these
recommendations, it doesn't mean your work is over," he said. "It's still
really important to reach out to affected communities and receive their
input." BART's accessibility efforts are not just important for users with
disabilities, Moore said. In the future, he said, accessible design will
ensure that Web sites are compatible with a broad range of devices, such as
handheld computers.

"Going down this road is inevitable for all of us," he said. "We're going to
have to be serving content to varied sources. This is a good start."
Received on Wednesday, 31 March 1999 20:17:41 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 13 October 2015 16:21:03 UTC