[orca-list] Orca dev resource

[Alex Midence <alex midence gmail com>]

Good day,

I wonder if someone might point me to a document where I might find
something detailing how Orca approaches making an app accessible.
I've been curious about this for some time.  I want to understand how
some things can be accessible to it while others cannot.  The whole QT
thing has me baffled, for instance.  If QT exposes all its controls
and such with labels and things as it advertises in their site, how
does that information elude ORca?  Also, WXwidgets is another thing.
I've used a few wxwidgets apps in Windows recently and they worked
pretty well for the most part.  Code::blocks is the latest thing I
used and it was all right except for the rad tool.  Anyway, when I
tried it in Gnome, Orca can't read the dialogs well for some reason
and text entry fields in other things like Geany and even AbiWord
which is gtk+ don't read back what is input.  Where is the break in
communication with Orca and the software?  Is there any way to "show"
Orca how to use other means for getting accessibility information
besides at-spi?  I'm sorry for all the questions.  I really wish to
understand.  If there's a page somewhere for me to browse where this
stuff is explained in a few paragraphs, please let me know.  I'm
learning c++ right now and would like to be able to write some apps
that I can use cross-platform with a GUI without having to rewrite an
interface each time I want to use it in another platform.  Gtk+ isn't
accessible in Windows and wxwidgets isn't great in Linux, and QT is
spotty in windows but not accessible currently in Gnome.

Sorry for the length,
Alex M