New issue
Advanced search Search tips

Issue 796945 link

Starred by 1 user
Status: Untriaged
Owner: ----
Cc:
dtseng@chromium.org
lpalmaro@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome , Mac
Pri: 2
Type: Bug
Team-Accessibility



Sign in to add a comment

Views needs a better way to know when to ignore a node for accessibility

Project Member Reported by dmazz...@chromium.org, Dec 21 2017 
On Mac, certain elements in the Views tree need to be leaf nodes for accessibility - we don't want their children in the accessibility tree. @patricialor added this change to support this:

https://codereview.chromium.org/2119413004

It currently works by setting the role to IGNORED.

As we're trying to share more Views accessibility code with Chrome OS, we need a better cross-platform solution. ChromeVox isn't aware of the IGNORED role. Perhaps this needs to be supported at a lower level in Views accessibility so that a View can override its list of children for accessibility, or maybe something simpler like it can just mark itself as a leaf node.

Perhaps we can even do that automatically for many common cases, like Views with certain widget roles with no focusable descendants can safely be marked as leafs.

Comment 1 by dtseng@chromium.org, Dec 21 2017 

To clarify things:
- a view gets the ignored role when the view is !IsDrawn() (follow the calls downward from IsViewAccessibilityFocusable. The other requirement is that it is focus behavior   != never.

I don't like either of these conditions because
1. IsDrawn()
walks up the entire ancestry and only returns true if all ancestors are drawn. Are there cases where an ancestor is not drawn, but a child is? Perhaps this one is ok.

2. focus behavior never. This one isn't good because it conflates two different things: accessibility focus and system focus. Accessibility focus is typically far more extensive than system focus (you pretty want to go everywhere with any visible content and even sometimes with non-visible content).

Comment 2 by dtseng@chromium.org, Dec 21 2017

Summary: Views needs a better way to know when to ignore a node (was: Views needs a cross-platform solution to make a node into a "leaf" node)

Comment 3 by dtseng@chromium.org, Dec 21 2017

Summary: Views needs a better way to know when to ignore a node for accessibility (was: Views needs a better way to know when to ignore a node)
Project Member

Comment 4 by sheriffbot@chromium.org, Dec 24

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
►

Sign in to add a comment