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

RE: Testing web page accessibility by phone

From: phoenixl <phoenixl@sonic.net>
Date: Thu, 30 May 2002 08:13:14 -0700
Message-Id: <200205301513.g4UFDEq4023889@newbolt.sonic.net>
To: foliot@bytowninternet.com, phoenixl@sonic.net, w3c-wai-ig@w3.org


Going to to the original question of user testing by phone.  What user testing
(rather than syntax testing) would need to be done to determine if
there are actually as few barriers as possible to the thought/content being
conveyed in our pages?


>> Scott
>> PS  Just a thought on "Accessible is accessible to all".  In a
>> book called,
>> "Johnny Got His Gun", the main character lost all four limbs, sight
>> and hearing.  If web pages aren't accessible to him, then they aren't
>> accessible?
>To him.  Trick questions not allowed <grin>.
>Seriously, if a user was faced with these barriers would they be able to use
>the internet at all?
>Let's assume that if the user had neither sight, hearing, or mobility then
>presumably communcication would be via some form of tactile transmission;
>I've seen braille output pads connected to computers, as well as braille
>printers so the technology exists.  In your scenario the user could probably
>not use an "off-the-shelf" application, but given enough desire and money
>the possibility of a custom adaptation is not far fetched... thus if the
>content of your web site could be interpreted by one of the braille type
>(tactile) transmitters, then, maybe, yes pages *could* be made accessible to
>the user.
>The point is, as developers we need to stop second guessing about *how*
>users access our pages... leave that to them.  Our goal is to ensure that
>there are as few barriers as possible to the thought/content being conveyed
>in our pages.  It's about knowledge, not transmission.
Received on Thursday, 30 May 2002 11:14:08 UTC

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