- From: Dan Burzo via GitHub <sysbot+gh@w3.org>
- Date: Tue, 07 Mar 2023 10:26:18 +0000
- To: public-css-archive@w3.org
I am mainly interested in the case where `speak: always;` overrides `display: none;` or `visibility: hidden;` to render to speech information otherwise not presented to any type of assistive technology. It sounds like presenting the information aurally would entail some sort of indirect effect on the accessibility tree to facilitate it. I understood @fantasai's [original message](#issue-969485866) in this thread as a task to express what this overriding of `display` and `visibility` properties entails, more formally. In regards to [your comment](#issuecomment-1456502339), a combination of `speak: always;` and `display: none;` is exactly the combination I'm hoping could function as a sort of `aria-hidden=false` without the burden of existing, incorrect usage. > Can you describe more about what you mean by sequential navigation in this context? I meant sequential focus via the Tab key. A specific use-case I had in mind, related to the `.visually-hidden` discussion, was "Skip to content" links that are often coded to become visible upon focus. I was hoping "visible upon focus" may be expressed more succinctly with `visibility: hidden; speak: always;` and still have the element available for Tab navigation, but I realize that's a thought that may be too nebulous and far removed from the issue at hand. -- GitHub Notification of comment by danburzo Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6515#issuecomment-1457922750 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 10:26:19 UTC