- From: Morgan Rae Reschenberg via GitHub <sysbot+gh@w3.org>
- Date: Wed, 24 Mar 2021 16:36:32 +0000
- To: public-css-archive@w3.org
I brought this up at our last a11y team meeting, and the general consensus was exposing offscreen content-visibility:auto content to AT's is important, and if the cost of doing that is causing some hidden content to render into the tree temporarily (until style comp), then that's a better tradeoff than not exposing the content at all. In general, we're fine with the Chrome approach. Technically, neither case fits with what AT's expect currently. The discussion on the call today seemed to indicate we're looking for a solution that maintains the tree invariants AT's expect. In that case, I think we've identified style computation as a necessary part of that solution. I'd like to flag here that doing style comp for AT's only is something we'd like to avoid because it has the potential to expose whether or not a user is using an AT. In our view, that tradeoff is also worse than rendering all content into the tree. With all that said, I think it might be worthwhile to consider modifying content-visibility such that style comp does happen, but painting doesn't -- that'd still allow UA's to optimise a bit without sacrificing AT experience. -- GitHub Notification of comment by MReschenberg Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5857#issuecomment-805977536 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 16:36:34 UTC