[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [platform-swt-dev] SWT_AWT and Accessibility
|
Well.. i just made an interesting discovery...
if you start jaws FIRST then your java app.. it does appear to pick up the
assistive text in both swing and swt panels.
If you start it AFTER your app. Then it will only see swt assistive text.
James Corbett - you may have more experience with this than anyone .. have
you seen this behavor before?
Thanks,
Jamie M. Guillemette
IT Solutions Developer
TD Enterprise Technology Solutions
275 Dundas Street, 11th Floor, London
(519) 663-1952
"Corbett,
James"
<James.Corb To
ett@cra-arc "Eclipse Platform SWT component
.gc.ca> developers list."
Sent by: <platform-swt-dev@xxxxxxxxxxx>
platform-sw cc
t-dev-bounc
es@eclipse. Subject
org RE: [platform-swt-dev] SWT_AWT and
Accessibility
05/11/2007
09:39 AM
Please
respond to
"Eclipse
Platform
SWT
component
developers
list."
<platform-s
wt-dev@ecli
pse.org>
Greetings:
As a Blind developer myself using both Jaws and SWT I've encountered
similar issues while attempting to incorporate SWING and SWT into the same
project... my own take on this come down purely on the side of the Access
Bridge and its inherent flakyness from version to version as well as
version to version of JFW.
Could you be more specific in your issue, perhaps I've already crossed the
same ground.
Jim
-----Original Message-----
From: platform-swt-dev-bounces@xxxxxxxxxxx
[mailto:platform-swt-dev-bounces@xxxxxxxxxxx]
Sent: May 11, 2007 9:40 AM
To: Eclipse Platform SWT component developers list.
Cc: Eclipse Platform SWT component developers list.;
platform-swt-dev-bounces@xxxxxxxxxxx
Subject: Re: [platform-swt-dev] SWT_AWT and Accessibility
Hi Richard,
Got a quick question fory you. Given the current issue with swing embedded
in an eclipse application. Is it safe to assume that we would encounter the
same problem using IBM's HOD (host on demand) embedded within an eclipse
app. HOD using a swing graphics panel to present its UI.
Thanks,
Jamie M. Guillemette
IT Solutions Developer
TD Enterprise Technology Solutions
275 Dundas Street, 11th Floor, London
(519) 663-1952
Richard
Schwerdtfeg
er To
<schwer@us. "Eclipse Platform SWT component
ibm.com> developers list."
Sent by: <platform-swt-dev@xxxxxxxxxxx>
platform-sw cc
t-dev-bounc
es@eclipse. Subject
org Re: [platform-swt-dev] SWT_AWT and
Accessibility
05/10/2007
02:26 PM
Please
respond to
"Eclipse
Platform
SWT
component
developers
list."
<platform-s
wt-dev@ecli
pse.org>
Jaime should have a test case. I spoke with Freedom's CTO, Glen Gordon, and
if you can isolate all the swing pieces to a black hole (isolated area) you
might get that to work with the access bridge. Once you start mixing swing
components with SWT components then you get into a lot of problems with not
being able to reconstruct the window hierarchy in your screen reader which
leads to lots of other problems.
What I will say as this is not a "JAWS supported" situation so it may work
and it may not.
I spoke with Mike Cooper, in the Expeditor team, on the subject this
morning and he is going to install the access bridge and try things out
with JAWS. Beyond that someone would need to work with Sun to try and get
an access bridge replacement which uses IAccessible2. IAccessible2 will
give you access to many things, including rich text, which would be lost
when Swing uses Java2D to render it.
Rich
Rich Schwerdtfeger
Distinguished Engineer, SWG Accessibility Architect/Strategist
Chair, IBM Accessibility Architecture Review Board
blog: http://www.ibm.com/developerworks/blogs/page/schwer
(Embedded image moved to file: pic16740.gif)Inactive hide details for Steve
Northover <Steve_Northover@xxxxxxxxxx>Steve Northover
<Steve_Northover@xxxxxxxxxx>
Steve
Northover
<Steve_Nor
thover@ca. (Embedded image moved to file:
ibm.com> pic13217.gif)
Sent by: To
platform-s (Embedded image moved to
wt-dev-bou file: pic29521.gif)
nces@eclip "Eclipse Platform SWT
se.org component developers list."
<platform-swt-dev@eclipse.o
rg>
05/09/2007 (Embedded image moved to file:
04:28 PM pic00056.gif)
cc
(Embedded image moved to
Please respond to file: pic09448.gif)
"Eclipse Platform SWT component (Embedded image moved to file:
developers list." pic28661.gif)
<platform-swt-dev@xxxxxxxxxxx> Subject
(Embedded image moved to
file: pic31450.gif)
Re: [platform-swt-dev]
SWT_AWT and Accessibility
(Embedded image moved to file:
pic26337.gif)
(Embedded image moved to file:
pic00400.gif)
It still makes sense to have a test case and bug report to track this issue
and confirm that it does not work.
Richard Schwerdtfeger
<schwer@xxxxxxxxxx>
Sent by:
platform-swt-dev-bounces@ecl To
ipse.org "Eclipse Platform SWT component
developers list."
<platform-swt-dev@xxxxxxxxxxx>
05/09/2007 04:41 PM cc
"Eclipse Platform SWT component
developers list."
<platform-swt-dev@xxxxxxxxxxx>,
Please respond to platform-swt-dev-bounces@eclipse
"Eclipse Platform SWT .org
component developers list." Subject
<platform-swt-dev@eclipse.o Re: [platform-swt-dev] SWT_AWT
rg> and Accessibility
(Embedded image moved to file: pic24099.gif)
(Embedded image moved to file:
pic02253.gif)
Swing applications, currently, interoperate with assistive technologies
through the Java Acces Bridge. Assistive technologies access Swing
applications through a special Java access bridge dll provided by Sun. This
is not how assistive technologies access Eclipse applications. Eclipse
applications interoperate with assistive technologies, on Windows, using
MSAA, offscreen modeling (screen scraping), and propietary APIs used by
ActiveX plug-ins. Even if you installed the bridge, this would be
problematic for ATs as they would not be able to handle the mix between the
access bridge dll and MSAA.
We have developed an accessibility API extension to MSAA, called
IAccessible2 which when combined with MSAA will give you the same level of
rich interoperability as Java. We hope to implement support for it in
Eclipse along with Linux accessibility support. Sun would also need to do a
mapping from the Java Accessibility API ( referred to by Jamie) and
MSAA/IAccessible2. This would provide the consistent framework you desire.
Sun has not made that investment at this time. IAccessible2 should be fully
supported by JAWS and Window-Eyes in their next releases.
So, it is recommended that Swing not be used in Eclipse applications if you
would like them to be accessible. If possible, we recommend using an
existing SWT control.
Rich
Rich Schwerdtfeger
Distinguished Engineer, SWG Accessibility Architect/Strategist
Chair, IBM Accessibility Architecture Review Board
blog: http://www.ibm.com/developerworks/blogs/page/schwer
(Embedded image moved to file: pic28053.gif)Inactive hide details for Steve
Northover <Steve_Northover@xxxxxxxxxx>Steve Northover
<Steve_Northover@xxxxxxxxxx>
Steve Northover
<Steve_Northover@xxxxxxxxxx>
Sent by:
platform-swt-dev-bounces@xxxxxxxxxx (Embedded image moved to file:
g pic11555.gif)
To
05/09/2007 03:18 PM (Embedded image moved to
file: pic15202.gif)
"Eclipse Platform SWT
component developers
Please respond to list."
"Eclipse Platform SWT component <platform-swt-dev@eclipse
developers list." .org>
<platform-swt-dev@xxxxxxxxxxx> (Embedded image moved to file:
pic29780.gif)
cc
(Embedded image moved to
file: pic31353.gif)
(Embedded image moved to file:
pic12464.gif)
Subject
(Embedded image moved to
file: pic10374.gif)
Re: [platform-swt-dev]
SWT_AWT and Accessibility
(Embedded image moved to file:
pic11291.gif)
(Embedded image moved to file:
pic27058.gif)
Can you confirm that it is working properly running a small Swing only
example? If so, please create a bug report with a stand alone snippet.
jamie.guillemette@xxxxxx
Sent by:
platform-swt-dev-bounces@xxxxxxxxxxx
To
platform-swt-dev@ec
05/09/2007 04:10 PM lipse.org
cc
(Embedded image
moved to file:
pic05687.gif)
Please respond to Subject
"Eclipse Platform SWT component developers [platform-swt-dev]
list." <platform-swt-dev@xxxxxxxxxxx> SWT_AWT and
Accessibility
(Embedded image moved to
file: pic09283.gif)
(Embedded image moved to
file: pic02531.gif)
Hi All,
Im trying to find out if the SWT_AWT bridge allows accessibility data to
flow from Swing components back to SWT and out to Accessibility
applications.
I have an eclipse application that uses swing for many views. The SWT_AWT
bridge is used to allow the swing panel to be embedded in the views.
Our client relies on Jaws a screen reader application.
In Swing we would call the method getAcessibleContext().setName() or
setDescription() on any swing component. This provides the details the
screen reader needs
to have to work properly.
So far my intial attempts at making this work within our eclipse plugin
have failed. Our SWT components / frames work perfectly.
Does anyone know :
a) is accessiblity supported in swing panels via SWT_AWT?
b) if not is there a best practice work around?
Thanks,
Jamie M. Guillemette
IT Solutions Developer
TD Enterprise Technology Solutions
275 Dundas Street, 11th Floor, London
(519) 663-1952
********************
NOTICE OF CONFIDENTIALITY
This communication including any information transmitted with it is
intended only for the use of the addressees and is confidential.
If you are not an intended recipient or responsible for delivering
the message to an intended recipient, any review, disclosure,
conversion to hard copy, dissemination, reproduction or other use
of any part of this communication is strictly prohibited, as is the
taking or omitting of any action in reliance upon this communication.
If you receive this communication in error or without authorization
please notify us immediately by return e-mail or otherwise and
permanently delete the entire communication from any computer,
disk drive, or other storage medium.
If the above disclaimer is not properly readable, it can be found at
www.td.com/legal
AVERTISSEMENT DE CONFIDENTIALITE
Ce courriel, ainsi que tout renseignement ci-inclus, destiné uniquement
aux destinataires susmentionnés, est confidentiel. Si vous
n’êtes pas le destinataire prévu ou un agent responsable de la
livraison de ce courriel, tout examen, divulgation, copie, impression,
reproduction, distribution, ou autre utilisation d’une partie de ce
courriel est strictement interdit de même que toute intervention ou
abstraction à cet égard. Si vous avez reçu ce message par erreur ou
sans autorisation, veuillez en aviser immédiatement l’expéditeur par
retour de courriel ou par un autre moyen et supprimer immédiatement
cette communication entière de tout système électronique.
Si l'avis de non-responsabilité ci-dessus n'est pas lisible, vous
pouvez le consulter à www.td.com/francais/legale
_______________________________________________
platform-swt-dev mailing list
platform-swt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-swt-dev
_______________________________________________
platform-swt-dev mailing list
platform-swt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-swt-dev
(Embedded image moved to file: pic18442.gif)
_______________________________________________
platform-swt-dev mailing list
platform-swt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-swt-dev
_______________________________________________
platform-swt-dev mailing list
platform-swt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-swt-dev
_______________________________________________
platform-swt-dev mailing list
platform-swt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-swt-dev
_______________________________________________
platform-swt-dev mailing list
platform-swt-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/platform-swt-dev
