List Info

Thread:




country flaguser name
United States
2007-08-29 13:43:18
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 -----

us.ibm.com); background-repeat: no-repeat; " width="40%">
          "Gregory J. Rosmaita&quot; <oedipushicom.net&gt;
          Sent by: wai-xtech-requestw3.org

          08/14/2007 08:25 AM

us.ibm.com" border="0" alt="">
To
us.ibm.com" border="0" alt="">
wai-xtechw3.org
us.ibm.com" border="0" alt="">
cc
us.ibm.com" border="0" alt="">
us.ibm.com" border="0" alt="">
Subject
us.ibm.com" border="0" alt="">
D-Bus-based accessibility API [FWD]
us.ibm.com" border="0" alt="">us.ibm.com" border="0" alt="">


---------- Forwarded Message -----------
From: Olaf Schmidt <ojschmidtkde.org>;
To: accessibilitya11y.org
Cc: kde-accessibilitykde.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 -------


View Original Image
View Original Image
Re: D-Bus-based accessibility API
country flaguser name
Germany
2007-08-30 05:32:24
Hi Rich!

In the meantime I had a look at Trolltech's D-Bus sources
and have started to 
compare them with the IAccessible2 and AT-SPI APIs.

My first impression is that there is a very large common set
of APIs that is 
shared by all three, some APIs that are individual to only
one of the three, 
and some APIs that are missing on one of the three.

If this is true, then I am concerned myself, but it is more
likely that I did 
not fully and correctly understand the IAccessible2
approach.

I am waiting for Trolltech to answer my questions before I
publish the 
comparision.

Olaf
_______________________________________________
kde-accessibility mailing list
kde-accessibilitykde.org
https://mail.kde.org/mailman/listinfo/kde-accessibility

[1-2]

about | contact  Other archives ( Real Estate discussion Medical topics )