Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


With a working MSVC 2010 build of master /3-7  for Windows now able to 
finally get into the a11y support for Java Accessibility in Windows with
Java Access Bridge.

Two open BUGs  fdo#39833
<https://bugs.freedesktop.org/show_bug.cgi?id=39833>   and   fdo#56704
<https://bugs.freedesktop.org/show_bug.cgi?id=56704>  

fdo#39833 was an enhancement to add a check box to the Windows installer to
"support assistive technology tools" with a single well exposed action for
Windows users requiring AT.

fdo#56704 is initial results of a MSVC 2010 build of master /3-7 for
windows,  reporting that while Java Access Bridge mapping into Java
Accessibility was exposing AT roles enabling JAB and the assistive
technology tools  for windows was not happening consistently. And that the
fdo#39833 enhancement  of the "support assistive technology tools" check box
selection during installation was not really working well.

Kind of hope others with working Windows builds of master can confirm the
errant configuration and behavior using both methods of setting the
libreoffice registry  stanzas for EnableATToolSupport and the truncated user
profiles. 



--
View this message in context: 
http://nabble.documentfoundation.org/BUG-56704-a11y-EnableATToolSupport-registry-setting-unreliable-sporadic-Java-Accessibility-AT-suppors-tp4016596.html
Sent from the Dev mailing list archive at Nabble.com.

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.