Visualizing object hierarchy in treeview

[nvaccessAuto]

Reported by tvalusek on 2008-06-17 06:32
Since NVDA is free software, it can be used as a helper tool for sighted developers for making accessible apps. I think it would be very useful for them to see at a glance what is exposed to blind computer user, and since object hierarchy is a tree, it should be presented as a tree. The same applies to virtual buffers.

[nvaccessAuto]

Comment 1 by mdcurran on 2008-06-17 08:08
There are currently a few free tools available for sighted developers to see and navigate the accessibility hyerarchy of an application. Acc Explorer which comes with the MSAA tools from Microsoft, and Accessibility Probe (which apart from MSAA also supports IAccessible2) from www.eclipse.org/actf.
Sighted developers could also use object navigation, but while using the 'display' synth driver.
My opinion is that NVDA doesn't really need this built in, although I'm happy to hear other people's opinions on this before we think of closing it.

[nvaccessAuto]

Comment 2 by tvalusek on 2008-06-17 18:15
NVDA can use direct API access as well, thus modifying what a blind user can experience.

[nvaccessAuto]

Comment 3 by Bernd on 2009-02-22 02:04
This feature could be interesting for users who can see a litle bit so that they would unterstand the hirachical order better.

[nvaccessAuto]

Comment 4 by nvdakor on 2013-11-25 09:38
Hi,
Quite an old ticket...
There exists an add-on which allows a user to navigate the object hierarchy of an application via treeviews. This add-on also presents a few handy object attributes such as name, value and such.
the add-on is at:
https://github.com/cromarty/nvda-treespy.git
Thanks.

[LeonarddeR]

Given the abandoned state of this issue, this is probably not high on the priority list. Labelled as feature.

[bhavyashah]

@LeonarddeR I would say the P4 label is more appropriate than feature, since feature implies that this ticket may be tackled by NV Access as part of a future project, whereas P4 indicates that NV Access are unlikely to ever work on this, although a community code contribution may be considered by them. In #111 (comment), since @michaelDCurran actually suggested turning down this feature request after some discussion, I am not even sure whether we should accept/validate this feature request. Thoughts? @feerrenrut

[feerrenrut]

Well, this is not a bug, so the feature label seems appropriate. That said, you are right that it is not something that is likely to be tackled by NVAccess. If someone felt strongly enough about this to expand on this, I think we would be interested. In particular, I would be interested in the specifics of how this would help, there isn't really an in depth explanation of the use case on this issue, or what is missing from the other solutions proposed.