w3c / w3c/csswg-drafts

[css-speech-1] Useful values to drive TTS engines

Open
#13,402 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

css-speech-1
Dominant language
Bikeshed
Stars
4.9k
Forks
816
PR merge metrics
PR metrics pending

Description

As the goal of CSS Speech is to override default TTS engines behavior / values, one could ask why define normal, medium, and auto values? To define default/initial values and to block the inheritance of undesired custom values I suppose.

If yes, it could be interesting to mention it, when defining these three values, and to point, in each definition, to the concepts of inheritance and defaulting, as defined by CSS Cascading and Inheritance Level 4.

As matter of fact, all specialists of aural rendering are not CSS specialists. They may be puzzled by these values (as I was on first reading). Cascading is the most difficult part of CSS for people who have no experience in object programming.

normal is a value for:

  • speak-as
  • voice-stress
  • voice-rate

medium is a value for:

  • voice-pitch
  • voice-range
  • voice-rate
  • voice-volume
  • pause-before
  • pause-after
  • pause
  • rest-before
  • rest-after
  • rest

auto is a value for:

  • speak
  • voice-duration

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the CSS Speech definitions for normal, medium, and auto values, then review the linked CSS Cascading and Inheritance Level 4 concepts of inheritance and defaulting. Done means the relevant value definitions explain their purpose and point readers to those concepts, covering the listed properties.

Written by the indexing model from the issue text.

Assessment

Tech stack
css
Domain
documentation
Issue type
Documentation
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.