Re: D-Bus-based accessibility API
"Mike Reiser" <[email protected]>
| Newsgroups | gmane.comp.kde.devel.accessibility |
|---|---|
| Message-ID | <00f101c7de86$5a562f10$b5e44e8b@mike5cb7a2e1b7> |
So I'm guessing we can use orca pretty soon on KDE? Mike ----- Original Message ----- From: "Olaf Schmidt" <[email protected]> To: <[email protected]> Cc: <[email protected]> Sent: Tuesday, August 14, 2007 8:15 AM Subject: [Kde-accessibility] D-Bus-based accessibility API > 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 > [email protected] > https://mail.kde.org/mailman/listinfo/kde-accessibility