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

Re: not jaws, just inaccessible:Fw: Inaccessible Web sites

From: Aaron Smith <aaron@gwmicro.com>
Date: Tue, 28 May 2002 08:24:00 -0500
Message-Id: <5.1.1.2.0.20020528081832.02d481d8@mail.gwmicro.com>
To: Patrick Burke <burke@ucla.edu>, Jerry Weichbrodt <gerald.g.weichbrodt@ived.gm.com>, w3c-wai-ig@w3.org
Ok, I'll give you that, but how is ad freezing be the responsibility of a 
screen reader? Why wouldn't a screen reader user use the same software that 
a sighted person would use (such as Proxomitron, RJT, JunkBuster, or 
Guidescope) to stop refreshing ads?

At 02:54 PM 5/24/2002 -0700, Patrick Burke wrote:

>Hmmm, is it the 10-second auto-refreshing ads? Does WinEyes have a method 
>for freezing them?
>
>Patrick
>
>At 01:05 PM 5/24/2002, Aaron Smith wrote:
>>Can you explain the inaccessibility of this page? Loaded with 
>>Window-Eyes, it reads well.
>>
>>At 04:03 PM 5/24/2002 -0400, Jerry Weichbrodt wrote:
>>
>>>Here's one more page that's an accessibility nightmare with JAWS, and it
>>>really surprises me.  http://www.iwanet.org/join/index.html
>
>

--
Aaron Smith
GW Micro
Phone: 260/489-3671
Fax: 260/489-2608
WWW: http://www.gwmicro.com
FTP: ftp://ftp.gwmicro.com
Technical Support & Web Development
Received on Tuesday, 28 May 2002 09:24:10 GMT

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