Apache OpenOffice (AOO) Bugzilla – Issue 71430
[a11y] In the Navigator window, the labels in the tree table should have a RELATION_NODE_CHILD_OF relation
Last modified: 2013-08-07 14:43:03 UTC
See also Orca bug #356060 which is currently blocked because of this bug. http://bugzilla.gnome.org/show_bug.cgi?id=356060 The Writer Navigator window contains a tree table of the various types of components making up the current document. The items in this tree table are labels. In Orca, in order to provide feedback to users on what node level they are at, those labels need to have a RELATION_NODE_CHILD_OF relation with their parent components.
ES->OBR: Please have a look. Tell me if I have a chance to check this with i.e. at-poke.
.
OBR->ES: yes, at-poke would display the relations if they were present. OBR->MT: we do not have this relation in our UNO API yet. If we add it, we probably should check http://developer.gnome.org/doc/API/2.0/atk/AtkRelation.html for additional missing items.
A11y => 2.3 PB...
pb: too late for 2.3 -> 2.4.
set target 3.0
pb -> richburridge: The navigator does not contain a tree but only a tree. So there is no need for a new relation.
> pb -> richburridge: The navigator does not contain a tree but only a tree. So > there is no need for a new relation. Sorry, I don't understand what you mean. Could you explain in more detail? Thanks.
Actually a colleague of mine intuited what you meant. Here is her reply. "Actually, I think he's just missing a word ("table"). 'The navigator does not contain a tree table but only a tree.' And that's true. But items in a tree I believe can still have the NODE_CHILD_OF relationship. And we need that relationship in order to provide access to the hierarchical level of the items being displayed." Reopening. Thanks.
The hierarchical relationship in a tree is expressed as parent/child relationship. Could you please explain in more detail why this is not sufficient ?
joaniediggs->OBR: If it is a question of sufficiency, then yes, I suppose it is sufficient. Other applications (or toolkits?) provide this relationship which makes it possible for Orca to provide the user with details about the hierarchy for any tree it encounters. In other words, Orca would JustWork(tm) in the Navigator tree were you to add this. If it is not possible for you to do so, we should be able to special-case the Navigator tree and look at the parents as you suggest.
To further add to this, as part of being a good AT-SPI implementation, tree like widgets are expected to expose the RELATION_NODE_CHILD_OF relation. It's not just for Orca. Thanks!
Both, ATK & AT-SPI documentation for RELATION_NODE_CHILD_OF, talk explicitly about tree tables, which is a separate role in ATK/AT-SPI. If this documentation is wrong, it should be fixed. As mentioned earlier, we do not have this relation in the UNO accessibility API yet, but given that IAccessible2 & Java do have it, we should probably add the type and enhance the tree implementation to expose it (instead of injecting the relation in the UNO <-> ATK bridge). Malte ?
Sounds reasonable... => 3.0
pb: fixed in cws pba11y01. Files changed: /offapi/com/sun/star/accessibility/AccessibleRelationType.idl 1.7.82.1 /vcl/unx/gtk/a11y/atkwrapper.cxx 1.9.14.1 /accessibility/source/extended/accessiblelistboxentry.cxx 1.3.16.1
pb -> es: please verify. Thx.
@PB/OBR: I can't find any difference between master/CWS in at-poke or accerciser. Nowhere to find a reference to RELATION_NODE_CHILD_OF. Did I miss something or is that fixed but failed??
Thanx to PB! for my records: - click in accerciser on a document item (ex: Table1) listed in the Navigator - Tabpage Interface viewer - Listbox "Relations" Verified in CWS pba11y01
This issue is closed automatically and wasn't rechecked in a current version of OOo. The fixed issue should be integrated in OOo since more than half a year. If you think this issue isn't fixed in a current version (OOo 3.1), please reopen it and change the field 'Target Milestone' accordingly. If you want to download a current version of OOo => http://download.openoffice.org/index.html If you want to know more about the handling of fixed/verified issues => http://wiki.services.openoffice.org/wiki/Handle_fixed_verified_issues