On Thu, 2007-07-05 at 21:13 +0200, Malte Timmermann wrote:
> I am not sure if all of you are aware of IAccessible2 (IA2,
> http://www.linux-foundation.org/en/Accessibility/IAccessible2 ), and the
> influence that it will have on Assistive Technology (AT) on Windows.
>
> OOo itself has a very rich Accessibility API, and is offering all needed
> information via this API.
>
> For this reason, IBM has "created" IAccessible2.
> Mainly they looked into OOo's Accessibility API, and extracted all
> things that are not covered by the Win32/MSAA combo.
One of the things they seem to get right (that OO.o's a11y didn't) is
the clear separation between localized & programmatic names for events;
eg. "click" vs. "GeButtonMachClickDinge" ;-) or whatever. Unfortunately
when writing some of the bridge to atk (which also has that separation),
it was not easy to do a good job in this area sadly.
> Implementing IA2 would be similar to what we are doing on GNOME now. A
> small bridge layer maps our UAA implementations to the systems
> Accessibility Architecture. In this case, this would mean implementing a
> bridge for MSAA and IA2.
Sure; as you say - it should be rather easy at least to get -something-
working. Of course, the real pain with these APIs is always the implicit
contracts, such as event ordering, state guarentees during event
emissions, lifecycle quirks etc.
Regards,
Michael.
--
[EMAIL PROTECTED] <><, Pseudo Engineer, itinerant idiot
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
