Folks should understand that the "Java Accessibility Bridge" foundation
for LibreOffice Assistive Technology and Accessibility Tools is one of
the primary components entirely dependent on a functional JRE? Java is
going to be with us in LibreOffice long after JRE 1.6 has been dropped
from Oracle support. Dealing with JRE 1.7 configuration is necessary now
and in the future.
So, JRE 1.6u34 is the latest release of that branch and JRE 1.7u06 is
the latest of that branch. But, both are completely functional with
LibreOffice when properly configured, and both support Java
Accessibility Bridge and Assistive Technology and the Accessibility
Tools in LibreOffice.
The problem is when they are not configured correctly. Java Access
Bridge, LibreOffice AT, and LibreOffice in general require use of a
32-bit JRE to work seamlessly.
Users on 64-bit Windows are tripped up by the Oracle JRE installers (or
Ninite installer packaging) that generically install the 64-bit JRE. It
is the generic Windows centric installation--of executables copied into
the C:\Windows\System32 and C:\Windows\SysWOW64 folders that causes most
problems for LibreOffice Java Access Bridge dependent users of LO
Accessibility Tools. Simply put, the wrong version of the JRE gets
called.
To avoid that for JRE, JAB and LibreOffice AT users, forcing a proper
configuration requires removal of the generic executables and inclusion
of the JRE into system PATH variable. Convention says use a JAVA_HOME
variable, but the full path to the JRE bin directory is just as
effective, e.g. append ";C:\Program Files (x86)\Java\jre7\bin" to the
PATH variable.
Sounds simplistic, but if you start with a solid 32-bit JRE install, the
JAB will go on cleanly (use the JWin tool). Follow that with NVDA or
commercial screen reader, and then a LibreOffice 3.6.1 installation.
Which now offers Accessibility support during installation and startup.
Additionally, for users that had a JRE 1.6 installation and had problems
following a JRE 1.7 upgrade. Doing an "upgrade" to JRE 1.7 does not
clear the JRE 1.6 configuration that LibreOffice had been using--and
suspect there are JAB and other assistive technologies that will also
have broken configurations. The most reliable way is to remove it all
and start from the JRE installation.
But for certain, with LibreOffice the configuration has to be manually
cleared--and allowed to rebuild with correct JRE 1.7 details. A JRE 1.6
installation would be just as trouble prone if it were not configured
correctly.
Stuart