This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
David to talk to Rich to get clarification around issue 108: http://www.w3.org/WAI/PF/Group/track/issues/108 CS: this is about ID's on the accessible tree nodes ... could add a bullet to the list in section 4.1 ... up to the user agent to get this right and authors should be free of having to worry about it DB: not sure we need to say anything ... if others do, I'm fine with that. CS: every node in the accessibility tree has an ID DB: in MSAA, you have a bunch of data that specifies an accessible object - use ID to communicate with AT CS: maybe something about managing IDs in the accessibility tree is the responsibility of the UA, not the author
Vendors use them to accessible objects from events, to stored accessible objects. IAccessible2::get_uniqueID
So what is needed in the UAIG?
http://accessibility.linuxfoundation.org/a11yspecs/ia2/docs/html/interface_i_accessible2.html#ac1342376cf195a6a6e9ee3b7e30ae3b
The IA2 spec says "This value is provided so the AT can have access to a unique runtime persistent identifier even when not handling an event for the object. An example of when this value is useful is if the AT wants to build a cache. The AT could cache the uniqueIDs in addition to other data being cached. When an event is fired the AT could map the uniqueID to its internal model. Thus, if there's a REORDER/SHOW/HIDE event the AT knows which part of the internal structure has been invalidated and can refetch just that part." We could probably put similar information into our document. We would want to qualify it with, 'where supported by desktop API'... Andi is this enough?
Is this something that goes in the accessible tree? If so, then I think it goes in section 4.1 General rules. It it unique to IAccessible2 or do the other APIs also have it?
(In reply to comment #5) Not sure what you mean by in the accessible tree... it isn't a node in the tree unto itself but is something any accessible object can return when an AT calls IAccessible2::uniqueID. I think it is only in IA2 and will be useful for ARIA 2.0 possible features...
Discussed at ARIA TF meeting July 18, 2010: http://www.w3.org/2010/07/19-pf-minutes.html#item04 Agreed that this is not an issue for the ARIA UAIG but should be logged against the future HTML 5 UAIG. Closing this bug and reassigning issue 108 to the HTML 5 UAIG.