Re: [orca-list] making gnome applications work better with orca
- From: Jason White <jason jasonjgw net>
- To: orca-list gnome org
- Subject: Re: [orca-list] making gnome applications work better with orca
- Date: Thu, 2 May 2013 15:02:59 +1000
Don Raikes <don raikes oracle com> wrote:
I have run into an application which is "almost" accessible. Many of the
controls are accessible, however, there are various scrollpanes which orca
cannot read at all.
To solve this, you need to find out why it's happening. The first step is to
collect Orca debug output, or run an AT-SPI monitoring tool, to ascertain what
the application is disclosing to Orca. If the inaccessible components are
custom user interface controls, they probably won't support the required ATK
interfaces and you'll need to enter the source code of the application and
make changes.
Unfortunately there isn't a good guide to this.
Essentially, if the application doesn't provide the information in the first
place, Orca can't read it. The most common reason for this is that the
developers of the application have written their own user interface
components, in which case there will be one or more interfaces that have to be
implemented.
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]