<html><body>
<p>If additional APIs were needed - why were they not brought back to the IA2 standards team in OpenA11y?<br>
<br>
Rich<br>
<br>
<br>
Rich Schwerdtfeger<br>
Distinguished Engineer, SWG Accessibility Architect/Strategist<br>
Chair, IBM Accessibility Architecture Review Board<br>
blog: <a href="http://www.ibm.com/developerworks/blogs/page/schwer">http://www.ibm.com/developerworks/blogs/page/schwer</a><br>
<font size="2" color="#800080">----- Forwarded by Richard Schwerdtfeger/Austin/IBM</font><font size="2" color="#800080"> on 08/29/2007 01:41 PM</font><font size="2" color="#800080"> -----</font><br>
<br>
<table width="100%" border="0" cellspacing="0" cellpadding="0">
<tr valign="top"><td style="background-image:url(cid:1__=09BBF9D5DFF53EAE8f9e8a93df938@us.ibm.com); background-repeat: no-repeat; " width="40%">
<ul>
<ul>
<ul>
<ul><b><font size="2">"Gregory J. Rosmaita" <oedipus@hicom.net></font></b><font size="2"> </font><br>
<font size="2">Sent by: wai-xtech-request@w3.org</font>
<p><font size="2">08/14/2007 08:25 AM</font></ul>
</ul>
</ul>
</ul>
</td><td width="60%">
<table width="100%" border="0" cellspacing="0" cellpadding="0">
<tr valign="top"><td width="1%"><img width="58" height="1" src="cid:2__=09BBF9D5DFF53EAE8f9e8a93df938@us.ibm.com" border="0" alt=""><br>
<div align="right"><font size="2">To</font></div></td><td width="100%"><img width="1" height="1" src="cid:2__=09BBF9D5DFF53EAE8f9e8a93df938@us.ibm.com" border="0" alt=""><br>
<font size="2">wai-xtech@w3.org</font></td></tr>
<tr valign="top"><td width="1%"><img width="58" height="1" src="cid:2__=09BBF9D5DFF53EAE8f9e8a93df938@us.ibm.com" border="0" alt=""><br>
<div align="right"><font size="2">cc</font></div></td><td width="100%"><img width="1" height="1" src="cid:2__=09BBF9D5DFF53EAE8f9e8a93df938@us.ibm.com" border="0" alt=""><br>
</td></tr>
<tr valign="top"><td width="1%"><img width="58" height="1" src="cid:2__=09BBF9D5DFF53EAE8f9e8a93df938@us.ibm.com" border="0" alt=""><br>
<div align="right"><font size="2">Subject</font></div></td><td width="100%"><img width="1" height="1" src="cid:2__=09BBF9D5DFF53EAE8f9e8a93df938@us.ibm.com" border="0" alt=""><br>
<font size="2">D-Bus-based accessibility API [FWD]</font></td></tr>
</table>
<table border="0" cellspacing="0" cellpadding="0">
<tr valign="top"><td width="58"><img width="1" height="1" src="cid:2__=09BBF9D5DFF53EAE8f9e8a93df938@us.ibm.com" border="0" alt=""></td><td width="336"><img width="1" height="1" src="cid:2__=09BBF9D5DFF53EAE8f9e8a93df938@us.ibm.com" border="0" alt=""></td></tr>
</table>
</td></tr>
</table>
<br>
<tt><br>
---------- Forwarded Message -----------<br>
From: Olaf Schmidt <ojschmidt@kde.org><br>
To: accessibility@a11y.org<br>
Cc: kde-accessibility@kde.org<br>
Sent: Tue, 14 Aug 2007 15:15:17 +0200<br>
Subject: [Accessibility] D-Bus-based accessibility API<br>
<br>
Hi!<br>
<br>
For those who are not subscribed to the Gnome accessibility list <br>
or heard otherwise:<br>
<br>
Trolltech have released the promised D-Bus-based accessibility <br>
API. They have made it available at: <br>
</tt><tt><a href="http://labs.trolltech.com/page/Projects/Accessibility/QDBusBridge">http://labs.trolltech.com/page/Projects/Accessibility/QDBusBridge</a></tt><tt><br>
<br>
They also wrote a poke tool:<br>
</tt><tt><a href="http://labs.trolltech.com/page/Projects/Accessibility/IAPoke">http://labs.trolltech.com/page/Projects/Accessibility/IAPoke</a></tt><tt><br>
<br>
Last but not least, they have a ported Dasher to use the API:<br>
</tt><tt><a href="http://labs.trolltech.com/page/Projects/Accessibility/QDasher">http://labs.trolltech.com/page/Projects/Accessibility/QDasher</a></tt><tt><br>
<br>
(They say that they plan to contribute their work back to the <br>
official Dasher repository once things it has matured a bit.)<br>
<br>
The API is close to both IAccessible2 and AT-SPI.<br>
<br>
If I understnad the approach that Trolltech has taken correctly, <br>
then they have:<br>
<br>
a) implemented everything that is in IAccessible2 (including the<br>
improvements that are missing in AT-SPI)<br>
<br>
b) implemented everything from AT-SPI that has been left out of<br>
IAccessible2 because it is available in MSAA<br>
<br>
c) _not_ implemented parts of AT-SPI that are unused by the <br>
existing assistive technologies and that have therefore also <br>
been left out in IAccessible2<br>
<br>
Olaf<br>
------- End of Forwarded Message -------<br>
<br>
<br>
</tt></body></html>