Date: prev next · Thread: first prev next last


David, Alex

Unfortunately, it is what we have to work with.  One of the devs,  Andras Timar  put together the 
check box feature on the Windows installer, in response to FDO Bugzilla enhancement 39833 - Add 
"Support assistive technology tools" option to installation process [accessibility] found here: 
https://bugs.freedesktop.org/show_bug.cgi?id=39833

It is a bit of an improvement, but has not been as reliable as is needed.

The checkbox during installation creates a Windows system variable "SAL_ACCESSIBILITY_ENABLED",  
which has an unpublished dependency on a working Java Runtime Environment with Java Access Bridge 
enabled.   If it all functions correctly, the result is reliable setting of the "Use a Java Runtime 
Environment" and "Support assistive technology tools" for all users of LibreOffice -- but it will 
hiccup if more than one system JRE is found.

Running a command line installation with MSIEXEC.EXE and disabling  global install  with an 
ALLUSERS=0 flag makes the installation just for the current user.

The SAL_ACCESSIBILITY_ENABLED variable is processed for each user only when LibreOffice is 
initially started, and it generates a stanza in the LibreOffice configuration file -- 
registrymodifications.xcu

The stanza inserted is:

<item 
oor:path="/org.openoffice.VCL/Settings/org.openoffice.VCL:ConfigurableSettings['Accessibility']">
<prop oor:name="EnableATToolSupport" oor:op="fuse" 
oor:type="xs:string"><value>[true|false]</value></prop>
</item>

 Value is set true on creation. But,  we've had trouble getting this to reliably assert, and as I 
said it has an unpublished requirement for a JRE with Java Access Bridge enabled.

The Windows registry .REG file I posted  generates the same registrymodifications.xcu stanza, but 
can be used to toggle it true or false bit  just for just the current user.  It is our traditional 
method -- carried over with OpenOffice source, and now also used  by Apache OpenOffice

What changed at the 4.1.0.4 and now 4.0.5.2 builds was inclusion of code needed for the Java 7 JREs 
to more correctly handle focus event notifications that were changed slightly by Oracle with Java 7.

James and Mic have worked hard to make NVDA functional with the limitations of the UNO 
Accessibility API that the Java JRE and JAB uses in Windows. Your issues with Calc cell contents 
are limitations in what is implemented and passed to the JAB for the Windows  users.

Apache OpenOffice has been working of a branch implementing the IAccessible2 (1.2) spec based on 
work IBM did originally for Symphony.  We've had a chance to work with a couple of builds--but 
we've been on hold while AOO got their 4.0.0 build out the door.  IAccessibile2 will replace the 
Java Access Bridge rendering of UNO Accessibility API events with a native 
Accessibility/Instrumentation  bridge for Windows use.   But there will also need to be some 
redesign and hopefully improvements of the core UNO Accessibility API--and because that will likely 
affect NSAccessibility on OS X and ATK - AT/SPI on Linux it could be some time yet before a 
LibreOffice implementation of IAccessibile2 is available.

Stuart




-- 
To unsubscribe e-mail to: accessibility+unsubscribe@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
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

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: 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.