V Stuart Foote
> Since you all can take code from OO, can't you take basically, all of
> their accessibility information and use it in LO? I mean, I stopped
> using JAWS years ago, but I heard from other people that JAWS works with
> OO? Would that be a lot of work? Taking all of the accessibility
> information from OO because OO is very accessible, just not updated or
> even nearly as stable.
Apache OpenOffice (AOO) uses the same IAccessible2 API, but unlike
LibreOffice they left the MSAA/IAccessible API in place, so there is
marginal Assistive Technology tool support in AOO with JAWS. And, nothing
that LibreOffice would care to implement--thank you.
Before its demise WindowsEyes had support for select IA2 based
applications--but never LibreOffice or AOO.
VFO/Freedom Scientific's refusal to support accessible events instrumented
with IA2 API has never made much sense to me personally, but their
insistence on Windows applications adopting Microsoft UI Automation (UIA)
brands them as a second rate player in the Free and Open Source Software
arena. It is not their business model--too bad if you are dependent on them.
LibreOffice as an OpenSource and cross platform development project is not
obliged to provide proprietary UIA bindings--an extension to "bridge" IA2 to
UIA could be developed--but we'll leave that to Freedom Scientific to
implement if they choose. We'll concentrate on making the native IA2/ATK &
AT-SPI/NSAccessibility bridges function cross platform against LibreOffices
internal accessibility modules.
For any JAWS user on Windows--LibreOffice is accessible at no cost, simply
install NVDA. Alternatively, ORCA on a Linux will do well, but if you need
more hand holding for a small fee the Hypra project's U.A.S. "Universally
Accessible operating System" is a first rate Linux Debian distribution.