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

Re: Skip Nav (was RE: "Think EUO, not SEO"/Google)

From: Kynn Bartlett <kynn@idyllmtn.com>
Date: Fri, 13 Jun 2003 16:28:47 -0700
Cc: Mike Rundle <phark@phark.net>, W3c-Wai-Ig <w3c-wai-ig@w3.org>
To: Charles McCathieNevile <charles@sidar.org>
Message-Id: <C7E0FABB-9DF6-11D7-AEE2-000393D9E692@idyllmtn.com>

On Friday, June 13, 2003, at 07:41 AM, Charles McCathieNevile wrote:
> As Bill said, this causes a problem for screen readers.

This is a problem with screenreaders.  :)  Really, the CSS specification
is pretty clear in allowing a user to specify style rules as being only
for screen display, or as being intended for aural display.

If an aural device chooses to ignore "aural" media type rules, and 
honor "screen" media type rules, that's honestly not the fault of the 
developer who is following the spec.

There are serious problems with compromising standards-compliant 
in order to account for broken implementations of the standard.  If a
screenreader user is complaining about only seeing what is on the
screen, and not hearing the "aural" content, that's something she should
take up with her screenreader developer.

(That's not to say that you couldn't, for example, generate a specific
screenreader Web interface in order to compensate for the broken 
just as you can do this with other broken software if you choose.  But 
you shouldn't be defacing Web designs because screenreaders want to act 
"screen" media instead of "aural" media.)


Kynn Bartlett <kynn@idyllmtn.com>                     http://kynn.com
Chief Technologist, Idyll Mountain                http://idyllmtn.com
Author, CSS in 24 Hours                       http://cssin24hours.com
Inland Anti-Empire Blog                      http://blog.kynn.com/iae
Shock & Awe Blog                           http://blog.kynn.com/shock
Received on Friday, 13 June 2003 19:23:36 UTC

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