Issue 29446 - need function that determines use of accessibility support.
Summary: need function that determines use of accessibility support.
Status: REOPENED
Alias: None
Product: General
Classification: Code
Component: code (show other issues)
Version: 680m38
Hardware: All All
: P3 Trivial (vote)
Target Milestone: AOO Later
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks: 29447
  Show dependency tree
 
Reported: 2004-05-24 14:12 UTC by joachim.lingner
Modified: 2013-08-13 12:03 UTC (History)
4 users (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description joachim.lingner 2004-05-24 14:12:32 UTC 
Please provide a platform - independent function that determines if the user
needs support for AT tools.
Comment 1 nospam4obr 2004-05-27 09:08:38 UTC 
Accepted.
Comment 2 joachim.lingner 2004-05-27 14:06:20 UTC 
.
Comment 3 Martin Hollmichel 2004-05-28 17:35:38 UTC 
according to the announcement on releases
(http://www.openoffice.org/servlets/ReadMsg?list=releases&msgNo=7503) this issue
will be re-targeted to OOo Later.
Comment 4 kay.ramme 2007-06-18 11:02:54 UTC 
IHMO, this belongs to the Framework -> changed component ...
Comment 5 nospam4obr 2008-03-12 15:20:17 UTC 
We no longer bridge to the Java accessibility API on Linux/Unix since OOo 2.0.3
and will do so on Windows as well soon (IAccessible2).

So the user will only need an accessible Java if (s)he runs code that uses Java
Swing, for which I think it is ok to have her/him go to Tools - Option - Java in
case not all Java installations have accessibility enabled.
Comment 6 joachim.lingner 2008-03-19 16:48:03 UTC 
I do not agree. An office could theoretically come with bundled extensions which
could use swing. In this case, the disabled user would prefer that the office
uses a Java with accessibility bridge from the beginning. I admit that the
usefulness of this function is now somehow less, but it is still there.
Also, if we say that a Java with accessibility bridge will NOT be selected
automatically anymore, then I would remove the code from the Java selection code
(jvmfwk). Therefore I suggest to give this issue to user experience and have
they decide before I remove the respective code.
Comment 7 joachim.lingner 2008-03-19 16:48:42 UTC 
.
Comment 8 bettina.haberer 2010-05-21 15:03:06 UTC 
To grep the issues easier via "requirements" I put the issues currently lying on
my owner to the owner "requirements".
Comment 9 Christophe Strobbe 2013-08-13 12:03:34 UTC 
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.