- From: vmpstr via GitHub <sysbot+gh@w3.org>
- Date: Wed, 17 Mar 2021 17:09:13 +0000
- To: public-css-archive@w3.org
To summarize: @atanassov raised a concern that if we expose content-visibility: auto subtrees, it means exposing things that are otherwise hidden (such as display: none) and that is not ok. > Rossen_: We can take a whole sale don't expose or expose it the right way. Anything outside of that will be broken behavior for a11y So, not exposing anything penalizes a11y users by hiding content which I don't think is a valid solution here, particularly because there is no way to force show this content in AX. I don't know of a way that we can expose the content the right way without forcing style resolution on content-visibility auto subtrees for accessibility only. This would change timing and increase the time to produce content for accessibility users compared to non-accessibility users. The expose-everything approach would reveal too much information, but I think the correct state can still be recovered with an appropriate use of aria labels, so I would like to not discount this approach altogether. -- GitHub Notification of comment by vmpstr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5857#issuecomment-801256599 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 17 March 2021 17:09:14 UTC