New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Correctly handle ARIA tree controls in browse mode when the tree isn't focusable #3573
Comments
Comment 1 by bgaraventa on 2013-10-13 00:46 Please refer back to the original bug to see what I mean regarding that NVDA does not convey that the control is a TreeView control at all when you arrow down the page in Browse Mode. |
Comment 2 by jteh on 2013-10-13 05:37 |
Comment 3 by jteh on 2013-10-13 05:39 |
Comment 4 by jteh on 2013-10-15 03:09 |
@jcsteh is this actually still an issue? Or has it been solved somewhere in the past? |
Yes, it's still broken. STR:
More complete test case at http://whatsock.com/tsg/Coding%20Arena/ARIA%20Trees/Tree%20%28External%20XML%29/demo.htm Previously, I said:
I've since realised we can instead call IAccessible::accSelection on the tree, which will return the selected item. That should generally also be a focusable item. We probably just want to render this node into the buffer, which also means the user would know which item is selected without having to enter focus mode. Same for list boxes. |
I have a branch geckoVbufRenderSelectedItem in my fork which renders the selected item for list boxes and trees. This fixes this issue, as well as improving the UX for list boxes and trees generally. Unfortunately, I'm being thwarted by two problems:
CC @michaelDCurran. |
Reported by jteh on 2013-10-11 06:24
Spun off ticket: #3023 (comment).
#3023 fixed handling of ARIA tree controls in browse mode that so that just the container is rendered, not its descendants. However, this only works when the tree itself is focusable. From what I can see, the ARIA spec doesn't specifically say trees have to be focusable. This seems odd to me, but unless I can find evidence otherwise in the spec, that's what we have ot deal with.
The only realistic solution I can think of is to walk through the entire tree to find the currently focused item when you press enter on the tree, which is pretty slow and ugly.
The text was updated successfully, but these errors were encountered: