The originating issue is here: https://bugzilla.mozilla.org/show_bug.cgi?id=617544
Alex's solution is here: https://wiki.mozilla.org/Accessibility/IA2_1.3#Anchor_target Due to the fact that this isn't a widespread issue I'd rather use a new relation than a new method to resolve the problem. I am proposing a new relation, hasFlowedTo. This is a generic name which could be suitable in many situations. A proposed text is: The object which has this relation is related to a group of additional objects, the sum of which make up a user's experience. The relation's target object is the object which has most recently been presented to the user. A concrete example is a section of a web page that has been navigated to via an in page link such as <a href="#foo">. Pete -- *Pete Brunet* a11ysoft - Accessibility Architecture and Development (512) 467-4706 (work), (512) 689-4155 (cell) Skype: pete.brunet IM: ptbrunet (AOL, Google), [email protected] (MSN) http://www.a11ysoft.com/about/ Ionosphere: WS4G On 6/28/2011 10:51 AM, Pete Brunet wrote: > Hi Alex, I did mean object attribute vs relation. At this point in > the discussion either of the three (object attribute, relation, > method) is OK with me. Since the requirement does not seem to be an > overwhelming one (from the input we have so far) perhaps adding an > object attribute or relation is the most pragmatic solution. > > Pete > > On 6/28/2011 5:05 AM, Alexander Surkov wrote: >> Hi, Pete. >> >> I don't recall who exactly came up with new interface suggestion, >> maybe it was me based on IA2 architecture in Gecko. >> >> Assuming you meant new relation rather than object attribute I >> believe relations approach work as generic approach. Any getter >> property that returns an object mapped well to relations mechanism, >> for example, IATable2::caption property can be exposed by relations. >> The question is when we want to introduce new method rather than >> reuse existing generic-propose method. >> >> Thank you. >> Alex. >> >> >> On Fri, Jun 24, 2011 at 12:41 PM, Pete Brunet <[email protected] >> <mailto:[email protected]>> wrote: >> >> Thanks Carolyn, >> >> Rich, When I read "accessibleDocument" I was thinking of the work >> done by Cathy Laws back around 2005. I finally found that >> document at >> >> http://accessibility.linuxfoundation.org/a11yspecs/atspi/adoc/ADOC_ATK.html >> Is this what you were thinking of? If so please start up a new >> thread to discuss that. >> >> By the way, ATK does have AtkDocument, documented at >> http://developer.gnome.org/atk/2.0/AtkDocument.html >> with these methods: >> atk_document_get_document_type >> atk_document_get_document >> atk_document_get_attribute_value >> atk_document_set_attribute_value >> atk_document_get_attributes >> atk_document_get_locale >> >> From what I remember we didn't see a need for the first 4 >> methods. We put the last two into the IAccessible2 interface so >> at this point IA2 doesn't have an IAccessibleDocument interface. >> >> Jamie, In the bug at >> https://bugzilla.mozilla.org/show_bug.cgi?id=617544 >> you proposed solving the problem with a new relation or a new >> accNavigate constant and in the new 1.3 document someone else, >> perhaps Alex, has proposed a new interface with one method, >> IAccessibleDocument::anchorTarget. (Perhaps that should have >> been currentAnchor?) Could the problem be solved with a new >> object attribute? >> >> Pete >>
_______________________________________________ Accessibility-ia2 mailing list [email protected] https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2
