Thanks for the Googleguy link, Chris --
<snip>
display:none also hides the element from some screen readers, the group
you might want to reach.
</snip>
display:none does hide content from screen readers, except for JAWS which
will read such content except when the declaration is inline. Similarly,
visibility:hidden is not read by some screen readers (again, JAWS will
read).
However, using display:none can be advantageous when one wants to hide
content from standards compliant visual browsers (for instance those that
understand @import) -- this content is for those using a non-standards
compliant browser, explaining why they are receiving a linearized basic
visual presentation rather than a more complex visual layout. Such messages
are not relevant for screen reader users, and so display:none is this case
can save the screen reader user from having to listen to this redundant
information.
<snip>
especially skip links are very handy for keyboard users
with perfect visibility. If they cannot see or reach the skip link, it
becomes useless.
</snip>
Absolutely -- is these cases, I use the off -page technique:
{
position: absolute;
left: 0px;
top: -500px;
width: 1px;
height: 1px;
overflow: hidden;
}
Then bring the content back to the viewport for keyboard users who are
tabbing through the site, using the relevant anchor pseudo-classes:
#skip a:active, #skip a:focus /* :focus for NS6/7 keyboard activation:
a:active for IE6 keyboard activation */
{
position:absolute;
left:0px;
top:0px;
width:auto;
height:auto;
font-family : Arial, Helvetica, sans-serif;
font-size : 12px;
color: #fff;
background: #000;
}
------------------------------
Leo Smith
www.leosweb.com
______________________________________________________________________
css-discuss [EMAIL-REMOVED]]
http://www.css-discuss.org/mailman/listinfo/css-d
List wiki/FAQ -- http://css-discuss.incutio.com/
Supported by evolt.org -- http://www.evolt.org/help_support_evolt/
