[Kde-accessibility] Fw: D-Bus-based accessibility API [FWD]

[Richard Schwerdtfeger]

If additional APIs were needed - why were they not brought back to the IA2
standards team in OpenA11y?

Rich


Rich Schwerdtfeger
Distinguished Engineer, SWG Accessibility Architect/Strategist
Chair, IBM Accessibility Architecture Review  Board
blog: http://www.ibm.com/developerworks/blogs/page/schwer
----- Forwarded by Richard Schwerdtfeger/Austin/IBM on 08/29/2007 01:41 PM
-----
                                                                           
             "Gregory J.                                                   
             Rosmaita"                                                     
             <oedipus at hicom.ne                                          To 
             t>                        wai-xtech at w3.org                    
             Sent by:                                                   cc 
             wai-xtech-request                                             
             @w3.org                                               Subject 
                                       D-Bus-based accessibility API [FWD] 
                                                                           
             08/14/2007 08:25                                              
             AM                                                            
                                                                           
                                                                           
                                                                           





---------- Forwarded Message -----------
From: Olaf Schmidt <ojschmidt at kde.org>
To: accessibility at a11y.org
Cc: kde-accessibility at kde.org
Sent: Tue, 14 Aug 2007 15:15:17 +0200
Subject: [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
------- End of Forwarded Message -------

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/kde-accessibility/attachments/20070829/f67e492c/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: pic04971.gif
Type: image/gif
Size: 1255 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/kde-accessibility/attachments/20070829/f67e492c/attachment.gif 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: ecblank.gif
Type: image/gif
Size: 45 bytes
Desc: not available
Url : http://mail.kde.org/pipermail/kde-accessibility/attachments/20070829/f67e492c/attachment-0001.gif