https://bugs.freedesktop.org/show_bug.cgi?id=56704
Priority: medium
Bug ID: 56704
Assignee: [email protected]
Summary: EnableATToolSupport value in LibreOffice registry is
not being reliably set resulting in sporadic Java
Accessibility AT support for Windows users
Severity: normal
Classification: Unclassified
OS: Windows (All)
Reporter: [email protected]
Hardware: x86-64 (AMD64)
Status: UNCONFIRMED
Version: 3.7.0.0.alpha0+ Master
Component: Libreoffice
Product: LibreOffice
Enabling Java Accessibility in LOdev -3-7 with creation of the
EnableATToolSupport stanza set true is not behaving consistently.
I am working with David Ostrovsky’s MSVC2010 build of LibO master (as still no
luck on successful TinderBox builds of Windows). So this is my first series of
run throughs with the current master / 3-7 source.
Following installation, LOdev launches and on this build the Assistive Tools
checkbox will hold state--since you have to check the box, then exit LibO, then
relaunch LibO--and does enable assistive tools. And Java Accessibility mappings
via the JAB are exposing AT roles! So we can confirm that Java Accessibility
via JAB occasionally works in windows LOdev master -3-7 branch.
But it can not be consistently enabled from the GUI.
So I don’t think we can call it 100% reliable yet; because even if I was able
to configure AT following installation, on subsequent launches I could not
consistently get the AT checkbox to hold state.
=-=-= Set Accessibility after installation from Tools -> Options =-=-=
There seems to be a problem in creating the LibreOffice registry on first use.
I wipe it clean on each installation cycle, and during install I don’t use the
“support assistive technology tools”--the enhancement of fdo#39833
(https://bugs.freedesktop.org/show_bug.cgi?id=39833 ).
To enable Assistive technology you first enable the Java Access Bridge. For JRE
> 1.7u6 done from command prompte with "jabswitch /enable".
Then in an LibreOffcie session navigate to the Tools -> Options -> Advanced –
Java options panel which shows a checkbox “Use a Java runtime environment”.
A list of JREs is populated--but there is no default radio button selection,
even if just a single JRE is detected, the radio buttons are all blank and one
of the JRE radio buttons must be manually toggled. If this selection code could
be reworked to select a default (preferably one detected "with accessibility
support", i.e. JAB) it would be useful.
Requirement for that: this JRE selection dialog is not exposed to Windows
MSAA/IAccessible or UI dialog—so it is a blind selection for AT dependent
users. Makes it a bit tough to correctly select a system JRE for Accessibility!
So, with a JRE selected, next on the Tools -> Options -> Accessibility tab try
the check box “Support assistive technology tools (program restart required).
And also the check box, “Use text selection in read-only text documents.” I OK
out and exit. Launch again and in the Options -> Accessibility menu “Use text
selection in read-only text documents” has remained checked, but the “Support
assistive technology tools…” does not.
Opened the registrymodification.xcu and manually edited the stanza for
VCL:ConfigurableSetting['Accessibility'] EnableATToolSupport from false to
true. When I make that manual edit--on subsequent LibO launches AT roles were
being exposed.
Verified that without the use Accessibility tool checkbox during installation,
that no SAL_ACCESSIBILITY_ENABLED system environment variable gets created in
registry from any of the toggle actions in Tools -> Options -> Accessibility.
IIRC that is to be expected from what the fdo#39833 enhancement does.
=-=-=Set the "support assistive technology tools" checkbox during install =-=-=
So, I removed everything and on next install cycle--this round I checked the
"support assistive technology tools" on the install panel.
Andras Timar can probably explain better, but IIRC he could not directly set
LibO registry values in registrymodification.xcu without doing MicroSoft
Installer custom actions in the MSI package. So instead installer sets an
environment variable SAL_ACCESSIBILITY_ENABLED which gets read for each first
use of LibO and based on that flag is supposed to write the
VCL:ConfigurableSetting['Accessibility'] EnableATToolSupport set as true into
each users registrymodification.xcu
But installing this way, in this LOdev -3-7 build, the registry creation
process does not complete and the accessibility & assistive technology tools
settings as well as the javasettings_Windows_x86.xml are not being fully
created--it looks like they receive some minimal template that is not
functional.
So, with this LOdev build, something is very broken with the "support assistive
technology tools" install checkbox--added to the recently reopened fdo#39833.
But neither method is resulting in reliable enabling of Assitive technology
tools for Windows with Java Accessibility and JAB.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
