- From: Mats Palmgren via GitHub <sysbot+gh@w3.org>
- Date: Wed, 24 Mar 2021 04:40:15 +0000
- To: public-css-archive@w3.org
Fwiw, my understanding of `speak-as` is that the intent is to provide an alternative _for speech synthesizers only_. For example, take the spec quote from the OP: >A counter style can be constructed with a meaning that is obvious visually, but impossible to meaningfully represent **via a speech synthesizer**, or possible but nonsensical **when naively read out**. The speak-as descriptor describes how to **synthesize the spoken form** of a counter formatted with the given counter style. (my emphasis). The rest of the spec contains phrases like "speaks a UA-defined phrase or audio cue", "being read out", "speak it as normal text in the content language", "how to pronounce the symbols", "read out as (in phonetic notation) /a/..." and "pronunciation". I don't see how any of that applies to AT other than speech synthesizers. Ideally, the UA should provide both the default form and the `speak-as` form and let the AT pick which to use. (The AT could even provide a way to access both forms.) -- GitHub Notification of comment by MatsPalmgren Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6040#issuecomment-805485843 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 24 March 2021 04:40:17 UTC