- From: Laurence ZAYSSER via GitHub <noreply@w3.org>
- Date: Tue, 03 Feb 2026 18:35:52 +0000
- To: public-css-archive@w3.org
LaurenceZaysser has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-speech-1] TTS default value == It seems that `normal` value has been defined to address the _default_ value of a property by the TTS engine. But so far, `normal` value has been attached to the following properties only: - speak-as - voice-stress - voice-rate It is not a value for these ones (with `medium` values): - voice-pitch - voice-range - voice-rate - voice-volume - pause-before - pause-after - pause - rest-before - rest-after - rest Sometimes `normal` and `medium` values coexist, as they do for `voice-rate` property. In fact, their meaning is supposed to be different: `normal `is a synonym for _default_, when `medium` is a shortcut for a _customized_ numeric value. Though, only `voice-rate` property can take both `normal` and `medium` values. Why? What not `voice-pitch`, `voice-range`, `voice-volume`? I am afraid, due to repeated changes, some incoherence has been introduced in the spec. Furthermore, `normal` is highly ambiguous between `default` and `medium`. Why don't you **make it clearer** and change `normal` to `default` when it means so, and for `medium` otherwise? And make these two values (`default` and `medium`) coexist anytime it makes sense. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13443 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 3 February 2026 18:35:53 UTC