CSS3 Speech module is now in last call state (Aug 18 , 2011) . Journey for making accessible web standards have come far from WCAG guidelines , SSML (Speech Synthesis Markup Language ) to CSS Speech
Here is the summary of what CSS Speech module provides.
CSS Speech standard specifies how to present the content in way which can be understood by speech synthesizers. Using CSS Speech module we can specify meta data like voice speed , pause information etc for content . This CSS information is used by User agents while rendering and producing final sound output for the content.
Typical usage for this would be
Machine to Human interaction ( e.g incase while you are driving car , car would read content for you online with appropriate pauses , breaks etc or your ebook reader will read the book , exactly the way it is read by humans)
CSS Speech is based on concept of Aural Box Model for content to be rendered in speech form . It is a conterpart for visual box model for visual presentation of content.
See the Visual box model for CSS and Aural Box Model below for similarities
The analogy between Visual Box model and Aural Box model is as follows
Hi benevolent001, thanks for highlighting this opportunity to get involved. And to reinforce the relationshp between coding for style and coding for accessibility note section 1.2 of the module:
1.2. Relationship with CSS2.1 The CSS Speech module is a re-work of the informative CSS2.1 Aural appendix, within which the "aural" media type was described, but also deprecated (in favor of the "speech" media type). Although the [CSS21] specification reserves the "speech" media type, it doesn't actually define the corresponding properties. This module describes the CSS properties that apply to the "speech" media type, and defines a new "box" model specifically for the aural dimension. [emphasis added]
... I really like the "illustration" of the aural box model in section 4 as well.
Does anyone have any insight on expected developments in the non-visual world? I mean support for these properties is dreadful at the moment, and I was just dismayed to read Do not use display:none to visually hide content intended for screen readers [456bereastreet.com] earlier this month as it seems a huge step backwards. Are we really going to see css providing us with the tools to support non-visual users in the near future?