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

Re: [css3-speech] comment on 'voice-volume' property

From: Daniel Weck <daniel.weck@gmail.com>
Date: Wed, 6 Jul 2011 19:48:26 +0100
Message-Id: <A175AD95-524B-4FAA-936E-768485172F49@gmail.com>
To: "www-style@w3.org style" <www-style@w3.org>, Daniel Glazman <daniel.glazman@disruptive-innovations.com>
Are you sure "muted" is the behavior you want? I would have thought  
that speak:none would be more appropriate, because 'silent' doesn't  
stop or pause the speech rendition, it merely sets the sound level to  
"not audible" (the audio effectively continues to play "in the  
background"). /Daniel

On 6 Jul 2011, at 18:02, Daniel Glazman wrote:

> Sorry to arrive late on that, but I notice an issue I raised about  
> CSS 2
> Aural Stylesheets eons ago (implemented them at that time) still  
> stands.
> A volume in modern appliances or SW is most often defined by two
> states: the real volume that is often a number, a %age or a list of
> enums, and a boolean state, normal or muted...
> I think the current 'voice-volume' property does not capture that. It
> has one immediate side-effect on users willing to rely on CSS 3  
> Speech:
> to mute the sound of a speech browser, the application has currently
> to switch to '0' or 'silent'. The original value is then
> forgotten in the computed value of 'voice-volume', forcing the app
> to keep track of it, and that could be avoided. In my mind, it
> even should be avoided.
> I suggest then to tweak the definition of 'voice-volume' as following:
> Value: 	[ <non-negative number> | <percentage> | silent | x-soft |
>          soft | medium | loud | x-loud | inherit ] muted?
> </Daniel>
Received on Wednesday, 6 July 2011 18:48:57 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:02 UTC