Trying to address the various concerns here but I think it's worth a phone call:
* ISimpleDOMNode is also a potential solution for the expert handlers question, so it may be worth adding to to ATK/IA2 as well. At least, this is a topic that I think is worth discussing in the standards calls. That would keep the symmetry with IA2. * I think we'd need to clarify usage guidelines -- e.g. when to use it * This should not be a difficult interface to implement in any other browser (Opera, WebKit) or Open Office. * It definitely doesn't have to be part of IA2 itself, but if it helps with the expert handlers problem then I think it should be. * To Surkov: to indicate changes, just fire a children-changed or EVENT_REORDER on the first ancestor that is also an IAccessible * And I think it's obvious that we still need IA2 no matter what. This definitely doesn't replace that. It just makes some things easier. - Aaron On 9/29/2008 5:15 AM, James Teh wrote: > I agree that ISimple* could be useful in places other than Mozilla, so > it should probably become some sort of standard, perhaps ratified by or > under the umbrella of OpenA11y. However, I'm not sure that IAccessible2 > is the best place for this to be incorporated: > * It does not relate in any way to the current IAccessible2 interfaces, > nor the current usage patterns for IAccessible2. It can be queried from > an IAccessible interface, but this doesn't necessarily mean it belongs > in the same standard. It is essentially a different accessibility API. > * As has already been pointed out, it creates cross-platform issues. As > I understand it, one of the major goals of IA2 is to minimise this as > much as possible by maintaining similarity to ATK, etc. wherever possible. > * Perhaps the biggest potential issue is the idea of IA2 conformance. If > an application or AT says it "is IAccessible2 enabled" or "implements > IAccessible2", does this mean it supports ISimple* or the current IA2 > interfaces? I acknowledge here that just because an application says it > supports IA2 doesn't mean it supports all of the interfaces, but one > knows that certain interfaces must be implemented to achieve certain > tasks. If there are two completely different methods for achieving the > same task (i.e. exposing complex documents), there is uncertainty as to > which will be used by a given application or AT. > * This idea of conformance also raises cross-platform concerns. For > example, a browser decides to "implement IAccessible2" by exposing > ISimple*, naively believing that IAccessible2 is very similar to ATK and > thus hoping that porting will be relatively easy. When they come to port > their application to Unix, they will quickly discover that they need to > support a whole new set of accessibility interfaces. If ISimple* does > become part of IA2, it needs to be very clearly documented that this > part of IA2 is not cross-platform at all. > > Also, it is perhaps worth considering why ATs are implementing support > for ISimple*, rather than IAccessible2. > * As Aaron pointed out, ISimple* is much more similar to the method used > to support IE. > * However, if IA2 is required for more advanced features, won't this > pose problems in future? > * Are there any other reasons that ATs refuse to implement IA2? > * Wouldn't implementing IA2 once and for all allow for many other > applications to be supported with much greater ease? > * If ISimple* was sufficient for DOM accessibility, why the move towards > IAccessible2 in the first place? > > Also, one other thought: if the raw document code is required for expert > handlers, perhaps this is a shortcoming of IA2 and a method should be > added to expose this. > > Just my thoughts. I certainly welcome feedback and clarifications. > > Jamie > > -- > James Teh > Email: [EMAIL PROTECTED] > WWW: http://www.jantrid.net/ > MSN Messenger: [EMAIL PROTECTED] > Jabber: [EMAIL PROTECTED] > Yahoo: jcs_teh > _______________________________________________ > 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
