[Kde-accessibility] D-Bus-based accessibility API

[Willie Walker]

Thanks Olaf!  

This is definitely interesting stuff, and I'm looking forward to
performance studies and real world experience with the new work.

I found the creation of a brand new API a cause for concern, however,
and have sent Harald a note on this.  While I'm awaiting a response, do
you know if Trolltech is looking to provide compatibility with existing
AT-SPI-based assistive technologies such as Orca?

Will

On Tue, 2007-08-14 at 15:15 +0200, Olaf Schmidt wrote:
> Hi!
> 
> For those who are not subscribed to the Gnome accessibility list or heard 
> otherwise:
> 
> Trolltech have released the promised D-Bus-based accessibility API.
> They have made it available at: 
> http://labs.trolltech.com/page/Projects/Accessibility/QDBusBridge
> 
> They also wrote a poke tool:
> http://labs.trolltech.com/page/Projects/Accessibility/IAPoke
> 
> Last but not least, they have a ported Dasher to use the API:
> http://labs.trolltech.com/page/Projects/Accessibility/QDasher
> 
> (They say that they plan to contribute their work back to the official Dasher 
> repository once things it has matured a bit.)
> 
> The API is close to both IAccessible2 and AT-SPI.
> 
> If I understnad the approach that Trolltech has taken correctly, then they 
> have:
> a) implemented everything that is in IAccessible2 (including the improvements 
> that are missing in AT-SPI)
> b) implemented everything from AT-SPI that has been left out of IAccessible2 
> because it is available in MSAA
> c) _not_ implemented parts of AT-SPI that are unused by the existing assistive 
> technologies and that have therefore also been left out in IAccessible2
> 
> Olaf
> _______________________________________________
> kde-accessibility mailing list
> kde-accessibility at kde.org
> https://mail.kde.org/mailman/listinfo/kde-accessibility