- From: Daniel Libby via GitHub <sysbot+gh@w3.org>
- Date: Fri, 04 Feb 2022 20:31:36 +0000
- To: public-css-archive@w3.org
From a conversation with the Narrator/UIA folks at Microsoft, their perspective is that content that is not visible to a sighted user should not be included in the accessibility tree. This determination is performed by the user agent (and specifically in Chromium by the pseudocode Chris referenced above). Therefore, they don't see the need for any such API at the platform accessibility API level. However, one part of the proposal that I think I'm missing - what would `isVisible()` return for an element in a `content-visibility: auto` subtree where contents are skipped? Per https://github.com/w3c/csswg-drafts/issues/5857, these elements are included in the accessibility tree (with the caveat that this may expose more than the user will see once the contents are activated). If that is the case, then perhaps an isVisible-like API for ATs could be useful - but given the principles around the decision to include that content, I don't know that we'd want to advise ATs to try and handle it separately than their existing logic. -- GitHub Notification of comment by dlibby- Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6850#issuecomment-1030328066 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 4 February 2022 20:31:38 UTC