Issue metadata
Sign in to add a comment
|
Flesh out invisible state usage |
||||||||||||||||||||||
Issue descriptionIn commit 916b6e43febdfbc42ea3deaf0efc69f335d8b011 the invisible state gets added manually to signal to accessibility to ignore a node. questions: 1. it is assumed in the commit that invisibility is only on the node. Elsewhere, we assume it applies recursively. 2. should we even allow subclasses to set invisible state? Should they set ignored role? 3. how should a client (e.g. ChromeVox) interpret it or should the accessibility tree simply prune the node (or subtree) from the accessibility tree?
,
Dec 21 2017
,
Dec 24
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 |
|||||||||||||||||||||||
Comment 1 by dtseng@chromium.org
, Dec 21 2017