[Accessibility] hello, finally

Aaron J. Seigo aseigo at olympusproject.org
Sat Apr 5 19:37:06 PST 2003


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello everyone...

sorry for the (uncharacteristic) delay in communication... been an 
unbelievable couple of weeks =/

anyways.. as a result of the last telephone conference, i would like to start 
discussion regarding some technical integration details of an accessability 
framework useful, usable and palletable to the range of applications that run 
on Linux.

for this to be a success and widely adopted, i would suggest that we need to 
have:

 o a solution that has minimal dependencies
 o is lightweight
 o is runtime, rather than compile time, dependant
 o does not require linking to monolithic third party application libraries

i'm not an accessability expert, as i've mentioned previously, but i have a 
rough idea of what sort of technologies will be easy to implement and get 
support for within the KDE framework. i'd assume that the requirements of the 
KDE project are going to be similar to many other open source software 
projects as well.

what would be excellent is if we (the KDE project) could implement support for 
a standard accessability framework at the KDE or Qt library level so that ALL 
KDE/Qt apps automagically gain accessability support as much as possible. it 
would also be excellent if the accessability technology used was such that it 
was loosely coupled to the end application and its libraries, i.e. by using a 
simple wire protocol (DCOP, or perhaps the upcoming DBUS as an even better 
option as it is/will be network transparent and politically easier to gain 
acceptance for).

the interaction would then look something like:

 Application -> App Support Lib -> DBUS -> Accessability daemon -> 
accessability software/hardware

for a concrete example:

 Konqueror -> Qt -> DBUG -> daemon -> [screen reader | braile keyboard]

i'm not very familiar with the ATK library as of yet, and i'm sure that at 
least some if not much of the preceding is probably elementary in concept in 
the accessability world. perhaps those who are more familiar with both 
accessability and the current open source solutions could provide some 
illumination. i'm simply hoping to start some discourse on the topic =)

- -- 
Aaron J. Seigo
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE: The 'K' is for 'kick ass'
http://www.kde.org       http://promo.kde.org/3.1/feature_guide.php
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQE+j6Dj1rcusafx20MRAmBZAJ4305hAi0Jeh85mHTytpIAGLy31KwCfT3K9
X79ivCP+UkdcefO3H0uIj/Q=
=BL17
-----END PGP SIGNATURE-----





More information about the Accessibility mailing list