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

While I agree with Kynn's point that screen readers are aural devices, 
and people who want to target aural devices differently should be able 
to rely on screen readers understanding the standard, the fact that 
they don't isn't particularly relevant to my argument.

There were two points I was making. The major one was that keyboard 
navigation is important for many people who are not screen reader 
users, and it is therefore helpful if it is visible.

The minor point was that using display:none to hide things except from 
screen readers is a bad move because in practise it hides them from 
common screen readers. It would be nice if one could use CSS to provide 
optimisations for aural browsing, but that seems to be a while away 

In any event, I would still like to be able to see the navigation links 
when I am browsing. Poor keyboard support is one of my big gripes 
against many otherwise nice browsers on MacOS X.



On Saturday, Jun 14, 2003, at 01:28 Europe/Zurich, Kynn Bartlett wrote:

> 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 
> instead
> honor "screen" media type rules, that's honestly not the fault of the 
> Web
> developer who is following the spec.
Charles McCathieNevile                          Fundación Sidar                      

Received on Saturday, 14 June 2003 05:46:54 UTC