- From: Léonie Watson via GitHub <sysbot+gh@w3.org>
- Date: Tue, 07 Mar 2023 08:54:48 +0000
- To: public-css-archive@w3.org
>...and it was unclear to me if that also implies reintroducing the element in sequential navigation, or presenting it in the accessibility tree. None of the Speech properties are intended to have a direct effect on the accessibility tree. The `speak` property may have an indirect effect though, because when it's set to `auto`, it's intended to mirror the `display` property. So if `display: none;` then the element with the `speak` property is handled as though `speak: none;` was set. Can you describe more about what you mean by sequential navigation in this context? In and of itself, the Speech properties are about changing the way content sounds when someone listens to content using synthetic speech (not just screen readers, but web readers, custom web readers using the Web Speech API and such). Returning to the `.visually-hidden` problem though, the idea I posted in https://github.com/w3c/csswg-drafts/issues/6515#issuecomment-1456502339 feels like it's worth exploring - trouble is of course that without any implementations, we don't have much to play with. I'm working on a prototype/polyfill for the Speech properties, but it uses the Web Speech API to simulate browser speech output - and there's no way to support screen readers at this point. -- GitHub Notification of comment by LJWatson Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6515#issuecomment-1457786368 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 7 March 2023 08:54:49 UTC