- From: Daniel Weck <daniel.weck@gmail.com>
- Date: Fri, 4 Feb 2011 11:36:38 +0000
- To: "www-style@w3.org list" <www-style@w3.org>
Hi Simon, with regards to implementations, please refer to: http://lists.w3.org/Archives/Public/www-style/2011Feb/0061.html As for the "speech" media type: it is mutually-exclusive with other types, but user-agents can still render in both aural and visual dimensions simultaneously, by virtue of the concept of "media groups": http://www.w3.org/TR/CSS21/media.html#media-groups http://www.w3.org/TR/CSS21/media.html#media-types Note that I do not wish to formally point to the CSS3 Syntax Module, because it is currently in an under-maintained state, but here are the links anyway (for reference only): http://www.w3.org/TR/css3-syntax/#media-groups http://www.w3.org/TR/css3-syntax/#media-types Now, as you know, there is a compiled table of CSS Speech-specific properties in the current draft, and below it there is a list of general CSS properties that affect TTS behavior: http://dev.w3.org/csswg/css3-speech/#property-index Once I have updated the latest online editor's draft, there will be a clear separation between "speak" and "speakability", which will describe more formally how "display:none" gets 'inherited' (so to speak) from the visual dimension into the aural space, and how authors can override this default behavior. I will also explicitly mention the impact of "visibility:hidden" in the aural dimension. Thank you for your feedback ! Regards, Daniel On 4 Feb 2011, at 04:32, Simon Fraser wrote: > I was initially rather confused about the interactions between the > "aural box model" and the "visual box model" when reading the speech > draft (<http://dev.w3.org/csswg/css3-speech/>) because I wasn't > thinking about the speech media type. > > I think the spec needs to mention the speech media type in the > introduction, and how this impacts which properties can influence > the spoken presentation of a page. A link to a table of CSS > properties, and their media types, would be useful. > > It strikes me that a if a web browser implements Speech, it will > need to support multiple presentations of the document at the same > time. I'd be interested to hear if there are any implementations of > Speech yet, given this level of complexity. > > Simon
Received on Friday, 4 February 2011 11:37:13 UTC