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

What's AT What's a screen reader

From: Jim Thatcher <jim@jimthatcher.com>
Date: Mon, 4 Apr 2005 11:53:19 -0500
To: "'David Woolley'" <david@djwhome.demon.co.uk>, <w3c-wai-ig@w3.org>
Message-ID: <001d01c53936$d2d50440$6501a8c0@jtcom2400>

David Woolley said:

> (Tools like JAWS are AT, not screen readers.)

I just couldn't leave it alone. What possesed you to day this? 

Jim
 
Accessibility Consulting: http://jimthatcher.com/
512-306-0931

-----Original Message-----
From: w3c-wai-ig-request@w3.org [mailto:w3c-wai-ig-request@w3.org] On Behalf
Of David Woolley
Sent: Saturday, April 02, 2005 1:34 AM
To: w3c-wai-ig@w3.org
Subject: Re: additional label question


> I am wondering, could you have have:
> .hide { display: none; }
> 
> And will screen readers still read that?

CSS conforming user agents will not render that in any medium.

Screen readers used on top of a CSS conforming visual browser obviously 
won't read it.

Assistive technology generally doesn't aim to be conforming (hence
the reason in the other thread that it tends to act as a visual 
browser for CSS when rendering to speech), but rather to try and
work best for the user in the real world.  However, I think it is
a slippery slope to deliberately mis-code pages to make them more
like bad HTML that the AT copes with (not that I'm saying that 
current products override display: none, one way or the other).

(Tools like JAWS are AT, not screen readers.)
Received on Monday, 4 April 2005 16:53:50 GMT

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