W3C home > Mailing lists > Public > www-style@w3.org > January 2011

RE: [css3-speech] ISSUE-153 speak: none; usage incompatible with other values of speak

From: Belov, Charles <Charles.Belov@sfmta.com>
Date: Wed, 12 Jan 2011 13:43:22 -0800
Message-ID: <E17F75B6E86AE842A57B4534F82D03769C3576@MTAMAIL.muni.sfgov.org>
To: <fantasai.lists@inkedblade.net>
Cc: <www-style@w3.org>
fantasai.lists@inkedblade.net wrote on Wednesday, January 12, 2011 10:53
AM
> CSS-ISSUE-153
> 
> http://www.w3.org/Style/CSS/Tracker/issues/153
> 
> The 'speak' property has two functions: one is to dual as the 
> speech equivalent of 'visibility', the other is to specify how 
> to speak the contents of an element.
> 
> This creates unintentional problems with, e.g.
> 
> acronym {
>   speak: spell-out;
> }
> 
> p.hide {
>   speak: none;
> }
> 
> <p>Thing to hide <acronym>WOAH</acronym> more stuff to hide</p>
> 
> The WOAH is suddenly injected into the speech rendering due 
> to the acronym rule, even though that is probably not what's intended.
> These functions should be separated into two properties, or 
> the 'none' value removed entirely.
> 

I do find the wording for none odd:

Suppresses aural rendering so that the element requires no time to
render. Note, however, that 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

What if you only want to suppress the sound and not the display
(although I'd want to see a use case that did not violate accessibility
standards)?

In any case, I believe one could code:

acronym {
  speak: spell-out;
}

p.hide {
  speak: none !important;
}

or perhaps

acronym {
  speak: spell-out;
}

p.hide,
p.hide * {
  speak: none;
}

Whether that is sufficient to alleviate concerns is another issue.

Hope this helps,
Charles Belov
SFMTA Webmaster
Received on Wednesday, 12 January 2011 21:47:20 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:36 GMT