DECLARATION OF CHARLES LETOURNEAU
CASE NO. 06-01802 MHP
la-863207
ROBERT A. NAEVE (CA SBN 106095)
RNaeve@mofo.com
MORRISON & FOERSTER LLP
19900 MacArthur Blvd.
Irvine, California 92612-2445
Telephone: (949) 251-7500
Facsimile: (949) 251-0900
DAVID F. MCDOWELL (CA SBN 125806)
SARVENAZ BAHAR (CA SBN 171556)
MICHAEL J. BOSTROM (CA SBN 211778)
DMcDowell@mofo.com
SBahar@mofo.com
MBostrom@mofo.com
MORRISON & FOERSTER LLP
555 West Fifth Street, Suite 3500
Los Angeles, California 90013-1024
Telephone: (213) 892-5200
Facsimile: (213) 892-5454
STUART C. PLUNKETT (CA SBN 187971)
SPlunkett@mofo.com
MORRISON & FOERSTER LLP
425 Market Street
San Francisco, CA 94105-2482
Telephone: (415) 268-7000
Facsimile: (415) 268-7522
Attorneys for Defendant
TARGET CORPORATION
UNITED STATES DISTRICT COURT
NORTHERN DISTRICT OF CALIFORNIA
SAN FRANCISCO DIVISION
NATIONAL FEDERATION OF THE BLIND,
the NATIONAL FEDERATION OF THE
BLIND OF CALIFORNIA, on behalf of their
members, and Bruce F. Sexton, on behalf of
himself and all others similarly situated,
Plaintiffs,
v.
TARGET CORPORATION,
Defendant.
Case No. C06-01802 MHP
DECLARATION OF CHARLES
LETOURNEAU IN SUPPORT OF
TARGET CORPORATION’S
OPPOSITION TO PLAINTIFFS’
MOTION FOR PRELIMINARY
INJUNCTION
Date: July 24, 2006
Time: 2:00 p.m.
Judge: The Honorable Marilyn Hall Patel
DECLARATION OF CHARLES LETOURNEAU
CASE NO. 06-01802 MHP 1
la-863207
DECLARATION OF CHARLES LETOURNEAU
I, Charles (Chuck) Letourneau, have personal knowledge of the facts set forth below,
and if called as a witness, I could and would testify under oath to the following:
Background
1. For the past ten years, I have been the president of and principal consultant for
Starling Access Services, a company that specializes in accessible Web site design, site
evaluations, and training.
2. From its establishment, I have been involved in the World Wide Web
Consortium’s (W3C) Web Accessibility Initiative. From 1997 to 1999, I co-chaired the
Initiative’s Web Content Accessibility Guidelines Working Group. I also served as the W3C’s
alternate representative to the Section 508 Advisory Committee1, a committee that was
organized pursuant to a congressional directive to recommend accessibility standards for the
purchase, development, and maintenance of electronic and information technology, which
includes web content (the “Section 508 Standards”).
3. I also spent two years leading a Website accessibility testing service for the
Canadian Treasury Board Secretariat, and six years working for the Canadian federal
government training employees with disabilities on how to use assistive technology in
conjunction with standard office software.
4. Further details of my 11 years of experience with Web accessibility, 16 years of
experience working with individuals with disabilities in connection with the use of assistive
technology, and my combined 24 years of experience with computers and technology, are
provided in my curriculum vitae, which is attached hereto as Exhibit A.
Accessing The Web Using Screen Readers
5. The blind community most commonly accesses Internet webpages using screen
readers. A screen reader is a software product that audibly reads the content of a computer
1 The advisory committee’s full name was The Electronic and Information Technology
Access Advisory Committee (“EITAAC”).


DECLARATION OF CHARLES LETOURNEAU
CASE NO. 06-01802 MHP 2
la-863207
screen using a speech synthesizer. Most screen readers are also capable of interpreting the
underlying code and structure of webpages, although some are better at it than others.
6. There are various screen reader programs used by the blind community. These
include Freedom Scientific’s JAWS program, GWMicro’s WindowEyes program, Dolphin’s
Hal Screen Reader, Choice Technology’s LookOUT program, ALVA Access Group, Inc.’s
Outspoken program, Apple’s VoiceOver, and The Speakup Project, a free Linux based
program. The most commonly used screen readers for the Windows Operating System are
JAWS and WindowEyes.
7. Like most technology, screen readers have evolved rapidly over the past five
years. For example, the current version of JAWS, which is 7.0,2 is noticeably superior to
JAWS 4.01, which came on the market in late 2001, early 2002. To illustrate:
· JAWS 7.0 also allows for improved access to non-HTML content, such as
content provided in Adobe PDF format, content displayed in scripts, and
content displayed using flash technology.
· JAWS 7.0 is much better at navigating a complex table of information, such as
a table that lists the prices and functionality of various laptop computers sold on
a retailer’s webpage.
· JAWS 7.0 also generally allows for easier navigation of websites.
Successive version of screen readers, including the successive versions of JAWS, have
continually allowed users greater access to websites. I am informed that Plaintiffs have
offered the declaration of one computer user who relies on JAWS 4.51 to access websites.
I believe that user would have an easier time accessing and navigating websites using the
current version of JAWS.
2 There is also a Beta version of JAWS, which is version 7.1, that is available for
download on the Internet. Version 7.1, however, is not yet available in stores.


DECLARATION OF CHARLES LETOURNEAU
CASE NO. 06-01802 MHP 3
la-863207
Guidelines on Accessibility
8. Web designers have a variety of accessibility guidelines to choose from when
creating new websites, or modifying existing websites to make them more accessible.3 These
include the Section 508 Standards, the Web Content Accessibility Guidelines (“WCAG”)
written by the W3C, Microsoft’s Accessibility Design Guidelines For the Web, IBM’s Web
Accessibility Guidelines, Canada’s Common Look and Feel Policy, the United Kingdom’s
Guidelines for Government Websites, Australia’s Guide to Minimum Website Standards
Accessibility, the State of Illinois’ Accessibility Guidelines, and the State of Connecticut’s
Accessibility Guidelines. Many other countries and states have also published accessibility
guidelines.
9. Strict adherence to any given set of guidelines, however, will not necessarily
render a website useable by a blind person. Web designers will often pull from more than one
set of guidelines, and draw from their own experience when designing new sites or modifying
existing sites to make them more accessible.
10. In North America, web designers often rely on the WCAG and the Section 508
Standards. These two sets of guidelines, however, are different from each other in a number of
respects. As I understand Plaintiffs’ expert, Dr. Thatcher, acknowledged at his deposition,
WCAG and the Section 508 Standards are different in wording, different in organization,
different in intention, and contain substantive differences. To cite a couple of examples:
· WCAG and The Section 508 Standards have different rules for dynamic
scripting content.4 The Section 508 Standards provide that the scripting
function must be accessible. WCAG provides that the information
conveyed through the scripting function must be made accessible even
when the user turns off the browser’s script reading function. There are
3 Of course, if a client requests that a web designer use a specific set of guidelines when
creating a new site or modifying an existing cite, the web designer will do so.
4 Dynamic scripting content includes such things as menus that pop up when the mouse
passes over an image on the screen.

DECLARATION OF CHARLES LETOURNEAU
CASE NO. 06-01802 MHP 4
la-863207
occasions where any user might turn off a browser’s scripting ability.
Some blind computer users might find scripted functions distracting or
difficult to use. Users who turn off their browser’s scripting function
should be able to access the scripted information in a WCAG compliant
website, but would not necessarily be able to access the same
information in a Section 508 compliant site.
· WCAG provides that web designers should “mark up documents with
the proper structural elements.” In essence, this means the web designer
should use appropriate headings and other content mark up to assist the
user in navigating the various information contained in the site. The
Section 508 Standards do not contain this requirement.
· The Section 508 Standards require websites to notify users if a web
session is to be timed out, and to allow the user sufficient time to
complete the Web transaction (i.e., a stock order, money transfer, or
merchandise purchase). This is an important requirement because, even
with the most accessible websites, it may take blind users longer than
sighted users to complete a Web transaction. WCAG, however, does
not include this requirement.
11. Even when a web designer relies upon accessibility guidelines, he or she must
nonetheless exercise a great deal of discretion. Indeed, a designer must exercise discretion in
organizing the content layout, choosing the most desirable headings, and implementing the
appropriate content mark ups.
12. The exercise of discretion is also required because the WCAG guidelines,
written between 1997 and 1999, and the Section 508 Standards, written between 1998 and
2000, do not reflect recent technological changes in how websites are programmed. The W3C
is in the process of revising WCAG, and The Section 508 Standards are slated for review this
coming September.

DECLARATION OF CHARLES LETOURNEAU
CASE NO. 06-01802 MHP 5
la-863207
Accessibility Depends On More Than Website Design
13. In my experience, a blind person’s ability to access any given website depends
on more than just the website’s design. It will depend on a host of additional factors including
the screen reader used, the browser used, the user’s technical abilities, the user’s familiarity
with the Internet in general (and his or her screen reader and browser in particular), and how
much time the user is willing to spend exploring the cite.
I declare under penalty of perjury under the laws of the United States that the foregoing
is true and correct.
Executed this 12th day of June 2006, at Ottawa, Ontario, Canada.
_______________________________________
Charles Letourneau