- From: James Craig via GitHub <sysbot+gh@w3.org>
- Date: Thu, 05 Jan 2017 07:53:52 +0000
- To: public-css-archive@w3.org
Comments on the current value definitions for [`speak`](https://www.w3.org/TR/css3-speech/#speaking-props-speak-as): > `auto` > Resolves to a computed value of `none` when `display` is `none`, otherwise resolves to a computed value of `auto` which yields a used value of `normal`. The spec should either make it clear most text-to-speech contexts are affected by both `display` and `visibility`, or it should declare this means "speak if visibly _rendered_". The "if rendered" option might require a new glossary term that makes it clear `opacity: 0` still counts as rendered even though `display: none` and `visibility: hidden` don't. > `normal` (Note: name may be changed) > The element is rendered aurally (regardless of its `display` value and the `display` and `speak` values of its ancestors). I think it's unlikely anyone has implemented this as defined. What user benefit is achieved by ignoring the ancestor cascade? Implementability could be questionable or challenging, too. Most implementations don't generate a render element for DOM elements matching `display: none` so it's unlikely there will be anything exposed to the accessibility APIs. I'm fairly certain this is the case in Gecko, WebKit, and Blink, but I am less certain about Edge. -- GitHub Notification of comment by cookiecrook Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/510#issuecomment-270584313 using your GitHub account
Received on Thursday, 5 January 2017 07:53:58 UTC