[orca-list] if you've ever wanted to try a qt application with orca ...

[Alex Midence <alex midence gmail com>]

Hi, list,

I posted this to the vinux group earlier today but thought that this
forum might be interested as wel.  Ther is now a debian package of the
qt-at-spi bridge it seems.  Actually, it's a package built by one of
the kde developers for the Kubuntu experimental port.  KDE, anyone?
Here is the ppa:

https://launchpad.net/~kubuntu-ppa/+archive/experimental

Does it work?  Well, here's a quote for your digestion.  Please take
note of the final sentence.  One of those bombshells people just sort
of drop casually on you:

title:  usb-creator in suse; accessibility in Qt, it speaks!

"More successful was packaging qt-at-spi, a plugin to get Qt talking
to AT-SPI2. Qt 4 has always had accessibility but while it has worked
on Windows and Mac it has never been plugged into the AT-SPI interface
used by Linux. This is because AT-SPI used Bonobo which used CORBA and
nobody wants to implement CORBA if they can at all avoid it. So Nokia
and others worked on AT-SPI2 which uses DBus. Unfortunately AT-SPI2
has been a long time coming, but now it is stabalising and getting
ready for use. Frederick Gladhorn has taken up the Qt plugin to talk
AT-SPI 2 and you can find it in the Kubuntu Experimental PPA.

It takes some fiddling to get it to work and the end result is crashy.
I had to install at-spi2-core, libatk-adaptor, python-pyatspi2 as well
as orca the screen reader. Then set some gconf settings to tell orca
to use AT-SPI2 (gconftool-2 --set /desktop/gnome/interface/at-spi-dbus
--type bool true; gconftool-2 --set
/desktop/gnome/interface/at-spi-corba --type bool false). Force some
environment variables export GTK_MODULES=gail:atk-bridge; export
QT_ACCESSIBILITY=1 and finally orca will read my Qt applications.
Yay."

Here's the url where I found this.
http://www.kdedevelopers.org/