David Goldfield wrote
What is very odd is that spreadsheet navigation works perfectly with NVDA
with OpenOffice and I'm under the impression that OO and LO are using the
same Iaccessible2 code.
Wrong assumption, so while the IAccessible2 (v 1.3) and the same native
Windows bridge is used by both projects, the Office components are rapidly
diverging. The LibreOffice Calc spreadsheet in particular has been
completely reworked from the OpenOffice.org era--similar refactoring has not
been done with Apache OpenOffice.
Unfortunately, with this new code base in LibreOffice, the triggering of
underlying accessibility events for cursor movements and accessible object
types have not been correctly done. The shortcomings affect builds for all
For Windows users, and indirectly the NVDA project, dumping a Java Runtime
Environment and Java Access Bridge dependency moves things along nicely.
But there is room for improvements both with the Windows IAccessible2 bridge
implementation as well as instrumenting the GUI with AT tool support. It is
not just with Calc, but it currently has some annoying behaviors that need
proper bug reporting and developer attention.
View this message in context:
Sent from the Accessibility mailing list archive at Nabble.com.
To unsubscribe e-mail to: firstname.lastname@example.org
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/accessibility/
All messages sent to this list will be publicly archived and cannot be deleted
Impressum (Legal Info)
: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (MPLv2
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our trademark policy