Reposting the response from Alex using the correct list address... -------- Original Message -------- Subject: Re: [Accessibility-ia2] Finding the most recent target of the most recent activation of an in page link Date: Thu, 9 Feb 2012 11:32:11 +0800 From: Alexander Surkov <[email protected]> To: [email protected] CC: IAccessible2 mailing list <[email protected]>
> If we do add a new method rather than a relationship, since we don't > currently have an IADocument interface, I'd prefer to add it to > IAccessible2_2. That would also be more generic, i.e. every kind of object > implements IAccessible2_2 but only a document object would implement > IADocument. Any example what the method called on IAccessible2_2 object could do if the object is different from document? > otherwise AT needs to crawl hierarchy. > > Alex, Please tell me more about the AT crawling the hierarchy. That's under assumption that AT knows about some accessible object and then AT wants to get anchor target so it needs to find document accessible for that. Maybe that's not a real usecase (for example more plausible usecase when AT is going to get anchor target when document gets focus). But this sounds like feature complete API. Anyway, if we don't want new IAccessibleDocument interface then we could add new relation to obtain document accessible object for the given accessible object to make sure this point is addressed. > We have three suggestions so far: > - hasFlowedTo > - isPositionedAt > - scrolledTo > > The first name might be a bit obscure, i.e. what is the concept of flowing? > The last one doesn't seem generic enough. So maybe isPositionedAt is a good > choice. What does everyone think? I'm fine with isPositionedAt too. Thank you. Alex. On Thu, Feb 9, 2012 at 11:14 AM, Pete Brunet <[email protected]> wrote: > On 9/6/11 10:45 PM, Alexander Surkov wrote: > > If you both think that new method is overkill then I'm fine to go with > relations approach. However this relation makes sense on document > accessible only and it'd be nice to introduce new method to obtain it, > > If we do add a new method rather than a relationship, since we don't > currently have an IADocument interface, I'd prefer to add it to > IAccessible2_2. That would also be more generic, i.e. every kind of object > implements IAccessible2_2 but only a document object would implement > IADocument. > > Regarding a relation vs a method, are there any issues that would argue for > one over the other? > > otherwise AT needs to crawl hierarchy. > > Alex, Please tell me more about the AT crawling the hierarchy. > > > Next IA2 spec is going to provide a method to get enumvariant for > relation of type, that could be used to get a single relation target. > > It can be named as 'scrolledTo' and be a generic propose relation, > i.e. whenever scrolling happens the relation target is changed. > > We have three suggestions so far: > - hasFlowedTo > - isPositionedAt > - scrolledTo > > The first name might be a bit obscure, i.e. what is the concept of flowing? > The last one doesn't seem generic enough. So maybe isPositionedAt is a good > choice. What does everyone think? > > > Thank you. > Alex. > > > On Sat, Sep 3, 2011 at 7:24 AM, James Teh <[email protected]> wrote: > > On 3/09/2011 7:50 AM, Pete Brunet wrote: > > 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 agree, and a relation was my original proposal. I think a relation is > a nice fit for this issue. Note that this definitely requires the new > method for getting a single relation without iteration. > > I am proposing a new > relation, hasFlowedTo. > > Hmm. I'm not sure about the name, but I can't come up with anything > better myself. Your explanation makes sense, but it sounds a little too > much like flowsFrom/flowsTo and I'm concerned that might cause confusion. > > Jamie > > -- > James Teh > Vice President, Developer > NV Access Inc, ABN 61773362390 > Email: [email protected] > Web site: http://www.nvaccess.org/ > _______________________________________________ > Accessibility-ia2 mailing list > [email protected] > https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2 > > _______________________________________________ > Accessibility-ia2 mailing list > [email protected] > https://lists.linux-foundation.org/mailman/listinfo/accessibility-ia2 > > > -- > 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
_______________________________________________ Accessibility-ia2 mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/accessibility-ia2
