W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > April to June 2002

Re: Testing web page accessibility by phone

From: David Poehlman <poehlman1@comcast.net>
Date: Fri, 31 May 2002 11:26:41 -0400
To: phoenixl <phoenixl@sonic.net>, w3c-wai-ig@w3.org
Message-id: <006f01c208b7$90f073f0$91e03244@DAVIDPOEHLMAN>

It does not help me at all.  A bunch of things are being confused here.
In order to speed the process of using a web page, one needs to take
into account several factors and none of them are listed here.  First,
One needs to make sure that access is not deminished for some in favor
of some. next, one needs to really know how to use their tool.  If you
are using jaws for windows for instance, there a number of
possibilities.  If a page has frames, you can get a list of the frames.
You can get a list of links and actually have them presented in several
orders depe ding on whether or not you have visitted them.  then it
becomes, visitted only, alphabetical list of all or tab ordered list of
all.  Newly added is the ability to be presented with a list of headings
on a page and this is usefull when pages are propperly marked up.

If she wants to talk to us, she should join the list.

----- Original Message -----
From: "phoenixl" <phoenixl@sonic.net>
To: <w3c-wai-ig@w3.org>
Sent: Friday, May 31, 2002 11:18 AM
Subject: Re: Testing web page accessibility by phone



Hi,

A blind woman sent me this message and said I could post it to this
mailing
list.  She has some interesting comments on the "time" issue.

Scott

-----------------------------------------------------------------------

    Hi Scott

    My name is _______________, and I am a blind computer user who has
    been on the Net since about 1993. I got to be part of that study the
    Nielsen-Norman Group did last year, and I was tremendously impressed
    by the thoroughness of their methods. I have also beta tested a few
    web sites and products, and am currently alpha testing an accessible
    online poker game. I think the best approach is to have the tester
    in voice contact with the company developer or researcher. The
    biggest hrudle in testing accessibility is to convey to the product
    or  software devloper the level of accessibility and usability
    experienced by the disabled user. A user with limited mobility would
    not be expected to spend twenty minutes locating and acitvating the
    necessary switch/button.etc., but frequently blind users are
    expected to hunt and search and go through extremely lengthy and
    frustrating processes in order to have equal access, and this is
    what is called "accessibility". Only by having the researcher
    experience the same length of time and frustrations the blind user
    experiences will the researcher comprehend all the possible
    shortcomings of the product. I have pointed this out a couple of
    times to other companies I have worked with, and they are always
    surprised when I point out that just because it takes a sighted user
    five seconds or less to visually see and click on an accessible
    button on a web page,  for example, does not mean that a blind user
    with a screen reader can locate and confirm this is the appropriate
    button in less than five minutes.

    In closing, the researcher needs to go through the precise
    experience the user has, and voice contact is the only method I can
    think of for this. I suppose a close second would be to give the
    user access to a web site where the researcher can track the user's
    process online through the server but this does not seem to offer
    the same level of feedback as live voice contact would.

    Hope this helps.
Received on Friday, 31 May 2002 11:27:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:14:04 GMT