https://issues.apache.org/ooo/show_bug.cgi?id=29446
Christophe Strobbe <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #9 from Christophe Strobbe <[email protected]> --- Update: 1. On Windows, the bridge between the internal accessibility API and the Java Accessibility API is being replaced by (a bridge to) IAccessible2; see issue 107914 and the plans for AOO 4.1. 2. If an extension uses Swing components instead of creating UI components through the UNO API, I think it should still implement the Java Accessibility API. Since Java 1.7 Update 6, the Java Access Bridge is being supplied as part of the JVM instead of a separate install (see https://blogs.oracle.com/javaaccessibility/entry/developer_preview_available_for_java and https://www.webaccessibility.com/blog/2012/08/30/jre-7-update-6-now-comes-bundled-with-the-java-access-bridge/). There may still be some issues with this solution, but the problem of a missing Java Access Bridge should slowly disappear. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. You are watching all bug changes.
