On 17/4/09 03:15, Russ Weakley wrote:
Of course, we'd all prefer to use the correct method, which is
"display:none" - but we have not been able to use this due to issues
with earlier versions of JAWS (content set to "display: none" was not
read aloud by these screen readers) - negatively affecting the very
people we were trying to assist. :(
Note, per the current CSS 2.1 spec, display is not a visual property
specifically, so it's probably not the correct method.
http://www.w3.org/TR/CSS21/visuren.html#display-prop :
"display" applies to all media types.
http://www.w3.org/TR/CSS21/aural.html#propdef-speak :
"speak: none;" "Suppresses aural rendering so that the element requires
no time to render" but "descendants may override this value and will be
spoken. (To be sure to suppress rendering of an element and its
descendants, use the 'display' property)."
That is to say, "display" might be more clearly named "render" (in
speech, in print, on screen, in braille, etc.).
If one assumed that screen readers should act as if they were aural or
braille browsers, then you could make a case that:
@media screen, projection {
.thing {
display: none;
}
}
would be a correct method. But this assumption doesn't really reflect
the actual approach taken by screen reader developers. All popular
screen readers ignore speech- and braille-specific CSS.
--
Benjamin Hawkes-Lewis
*******************************************************************
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
*******************************************************************
