- From: Daniel Libby via GitHub <sysbot+gh@w3.org>
- Date: Wed, 24 Mar 2021 00:34:45 +0000
- To: public-css-archive@w3.org
> If it was possible for us to provide a view into a partial document or a part of a document, with an annotation specifying that accessibility technology should request more of the document if it needs it, then that would solve the problem for sure. We have been looking into this more general problem ([see this explainer in WICG](https://github.com/WICG/accessible-loading-and-searching-of-content/blob/main/explainer.md)) and have an [experimental implementation](https://groups.google.com/a/chromium.org/g/blink-dev/c/etQ-LVhY6S4/m/QXG4acPAAwAJ) in Chromium to expose this to ATs on Windows (behind a flag). We're currently working with the Narrator team in Windows to implement experimental support for this new property in order to explore the user experience in practice. `content-visibility: auto` would then respond naturally to AT actions that cause it to scroll into (or close to) the viewport. That being said, there probably is something to be said for `content-visibility: auto` working for AT users 'out of the box' without authors needing to add extra ARIA semantics to ensure content is fully accessible. -- GitHub Notification of comment by dlibby- Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5857#issuecomment-805379898 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 00:34:47 UTC