- From: Xiaocheng Hu via GitHub <sysbot+gh@w3.org>
- Date: Tue, 16 Mar 2021 01:12:43 +0000
- To: public-css-archive@w3.org
Some more implementation feedback from Chrome: The way how `speak-as` is currently defined seems to aim at providing a vocal hint of the counter, which doesn't match the accessibility framework Chrome is using. Instead, Chrome heavily relies on the "alternative text", as mentioned by @dot-miniscule . Consequently, the implementation of `speak-as` in Chrome is reduced to generating the proper alternative text, which is either trivial (but misplaced) or unimplementable for each value: - `bullet`: trivial - `number`: it appears that we should always use the decimal string of the counter value as the alternative text, *regardless of the counter algorithm or the content language*; the screenreader will then read the decimal string in the content language. So the implementation is trivial, and the spec text doesn't seem very related - `words`: use the same counter text as the alternative text. Seems trivial, but again, we don't really have control on whether it's spoken as a number or words - `spell-out`: we don't have a way to provide vocal hints to the screenreader, so this is unimplementable. So I'm also looking for possibilities to revise `speak-as`, or introduce another descriptor that targets the alternative text directly. -- GitHub Notification of comment by xiaochengh Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6040#issuecomment-799868468 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 16 March 2021 01:12:44 UTC