tips for working with more at-spi compatible screen readers in Ubuntu Jaunty
Mgr. Janusz Chmiel
chmiel at phil.muni.cz
Thu May 14 20:09:54 UTC 2009
Dear users,
I would like to familiar You with ammazing possibility. This possibility
is, that You can use more than one screen reader in Ubuntu Jaunty in The
cases, when Orca will not read some specific list or other part of user
interface of a specific application. Eventhough Orca is now onlyone and The
best awailable Gnome screen reader, and i do not know about better solution,
i would like to write You some procedures, which You would find useful in
The case, if You accidentally break Your current Orca installation, or if
AYou would try to analyze user interface of some application which Orca can
not access. No everybody of us is advanced Python and C programming language
developer, so it would be good approach.
Firstly, i would like to inform You, that You can always install The fully
functioning and stable release of Orca by using gnome-orca package. This
package can be uninstalled or reinstalled by using
apt-get install gnome-orca
apt-get remove gnome-orca
So if You would for example accidentally download non functioning Orca
development snapshot, You would install it and You would lose Orca support,
You can always solve this issue by changing to The directory, where You
installed Orca snapshot from.
And as A root user in The gnome-terminal
ยจ
Type
make uninstall
Thank's to The ammazing feature of Linux architecture, You can even be
running Your Orca if it will atleast provide You basic feetback and You can
type those commands with speech support. Then, please terminate Orca by
using quit function.
Then, You can reinstall Orca from official Ubuntu repository by using
apt-get install gnome-orca
Before You will install Orca from source, please correctly install all
components before trying to use
./configure
make
make install
commands.
So for building Orca from source, You will need to execute The following
commands as A root user.
apt-get install libglib2.0-dev python-dev
apt-get install git-core gnome-common automake1.9
Then type
./configure
make
make install
If You will follow my instructions, You will be able to successfully install
LSR and Sue screen readers too.
And You can use those three screen readers without causing software
conflicts be each others.
Where You can find LSR and SUE screen readers? Those screen readers can be
downloaded by using provided direct links and those screen readers are also
written by using Python programming language and C programming language.
Please be aware, that LSR or Sue can not replace Orca and there can be some
stability or other bugs, but You can use those products for The situations,
while Orca has been accidentally broken, or if YOu would try to use those
screen readers for accessing some applications, which Orca is not able to
read. Those applications must be at-spi compatible, in other cases, also
those screen readers will not provide You access to those applications.
So You can download source code of LSR by using one of The following two
direct links.
http://download.gnome.org/sources/lsr/0.5/lsr-0.5.3.tar.gz
http://download.gnome.org/sources/lsr/0.5/lsr-0.5.3.tar.bz2
After decompressing those archives, You can install them like installing
Orca.
Where You can download SUE screen reader?
The best solution will be to use last development snapshot of this product,
so use svn to get this program by using The following hyperlink for
downloading source from SVN repository for SUE.
https://sue.svn.sourceforge.net/svnroot/sue/trunk
Or You can download The branch of this source by using
https://sue.svn.sourceforge.net/svnroot/sue/tags/SUE_0_4_0
SUE is based on LSR but core developers modified The source code and if
somebody want's to help developers during developing this product, everyone
is granted to do this.
Ubuntu Jaunty is now really stable and speech friendly distro, so do not
thesitate to try this distro, core developers are constantly updating this
distro, even complex parts of it like kernel image, at-spi.
I would strongly warn all users before building at-spi from source, it is
much more better to wait, if official build will be awailable by automatic
updates feature.
The kindness regards.
Janusz Chmiel
More information about the Ubuntu-accessibility
mailing list