[Accessibility] Mentioning Open a11y in an article

Steve Lee steve at fullmeasure.co.uk
Tue Oct 30 12:05:34 PDT 2007

Thanks George, the reason for the article is to introduce Python
programmers to accessibility and it's focus *is* GNOME, pyatspi and
accerciser, as that is central to much of  the action. Plus pyatspi
and accerciser afford a chance for a simple practical introduction and
we can hope that GNOME application developers may be encouraged to
test and implement their a11y.

As we are aiming at platform interoperability and harmonization I do
think it is worth mentioning in passing what is happening on other
platforms as well as the standardisation nurturing of Open a11y. NVDA
is a *Python* AT that uses IAccessible2 on Windows so it gets a

I also mention the Linux test platforms for reasons of completeness
and in the hope of attracting more developers.

I do keep rather quiet on Microsoft UIA as AFAIK Python does not
figure much (except perhaps via IronPython) ;-)


On 30/10/2007, George Kraft <gk4 at austin.ibm.com> wrote:
> I think the point of your article should be about python currently being
> the work horse of GNOME Accessibility via pyatspi used by Orca and
> Accerciser.
> http://live.gnome.org/GAP/Reengineering?action=AttachFile&do=get&target=gap-graph.png
> Why weaken your article by mentioning IAccessible2 for Windows and KDE
> accessibility which are not strictly based on AT-SPI; therefore, not
> directly relevant to the main pyatspi discussion?
> :-)
> George (gk4)

Steve Lee
Jambu - Alternative Access to Computers

More information about the Accessibility mailing list