Re: [orca-list] making gnome applications work better with orca

[Peter Vágner <pvdeejay gmail com>]

Hello,
I don't know this site verry well I have just skimmed it and tried the 
search for gtk, atk however I have found nothing that might be usefull 
here I am afraid.

Greetings

Peter
On 02.05.2013 12:12, Jude DaShiell wrote:
> Have you checked out http://www.fruitbasketdemos.org/ yet?
>
> On Thu, 2 May 2013, Peter V?gner wrote:
>
> > Hello,
> > Are there some simple examples somewhere?
> > If possible I would like to learn more on this but as I understand it the most
> > reliable method of working with this is by studying the source code.
> > The most known app where there are custom componentes where there are custom
> > atk interfaces implemented is evince. However I am afraid this is too complex
> > for a beginner.
> > I would like to start with some simple UI components such as buttons,
> > checkboxes etc. and then if If I will really be able to understand this move
> > on to more complicated components such as lists, tables and tab controls.
> >
> > Greetings
> >
> > Peter
> >
> > On 02.05.2013 07:02, Jason White wrote:
> > > 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.
> > >
> > > _______________________________________________
> > > orca-list mailing list
> > > orca-list gnome org
> > > https://mail.gnome.org/mailman/listinfo/orca-list
> > > Visit http://live.gnome.org/Orca for more information on Orca.
> > > The manual is at
> > > http://library.gnome.org/users/gnome-access-guide/nightly/ats-2.html
> > > The FAQ is at http://live.gnome.org/Orca/FrequentlyAskedQuestions
> > > Log bugs and feature requests at http://bugzilla.gnome.org
> > > Find out how to help at http://live.gnome.org/Orca/HowCanIHelp
> > _______________________________________________
> > orca-list mailing list
> > orca-list gnome org
> > https://mail.gnome.org/mailman/listinfo/orca-list
> > Visit http://live.gnome.org/Orca for more information on Orca.
> > The manual is at
> > http://library.gnome.org/users/gnome-access-guide/nightly/ats-2.html
> > The FAQ is at http://live.gnome.org/Orca/FrequentlyAskedQuestions
> > Log bugs and feature requests at http://bugzilla.gnome.org
> > Find out how to help at http://live.gnome.org/Orca/HowCanIHelp
> ---------------------------------------------------------------------------
> jude <jdashiel shellworld net>
> Microsoft, windows is accessible. why do blind people need screen readers?