Re: [csswg-drafts] [cssom-view] Proposal: add Element.isVisible[toDocument] to detect if element is visible in the document. (#6850)

I don't think the Narrator/UIA statement is detailed enough.
What about content that's scrolled off? That's not visible to a sighted
user, so shouldn't be included?
What about content that's behind other content in the z-order? Same Q.
What about content that's positioned offscreen (often done intentionally as
a technique to provide additional instructions to screen reader users).

IMO, what browsers do now is useful and works well with screen reader
expectations today. Not sure if there's a need to revisit any of this right
now TBH.
Regarding content-visibility: auto, it needs to be exposed so that screen
reader users can navigate by heading, etc. Unless someone sees a way around
that.

Aaron




On Fri, Feb 4, 2022 at 3:31 PM Daniel Libby ***@***.***>
wrote:

> 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 #5857
> <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.
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/w3c/csswg-drafts/issues/6850#issuecomment-1030328066>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AAKQAZUK6KKVWIALRN7ROIDUZQZTFANCNFSM5JFHLXJQ>
> .
> Triage notifications on the go with GitHub Mobile for iOS
> <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
> or Android
> <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
>
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>


-- 
GitHub Notification of comment by aleventhal
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6850#issuecomment-1030363803 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 21:29:25 UTC