[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [platform-swt-dev] SWT_AWT and Accessibility
|
Please move this discussion to a bug
report so that the issue and coorsponding discussion is tracked, others
can follow along, Freedom Scientific can comment etc. and we can work towards
a (possible) resolution.
Richard, once Jamie has created the
bug report, please add youself, put your comments there and get your pals
at Freedom Scientific involved!
jamie.guillemette@xxxxxx
Sent by: platform-swt-dev-bounces@xxxxxxxxxxx
05/10/2007 11:27 AM
Please respond to
"Eclipse Platform SWT component developers list."
<platform-swt-dev@xxxxxxxxxxx> |
|
To
| "Eclipse Platform SWT component
developers list." <platform-swt-dev@xxxxxxxxxxx>
|
cc
| "Eclipse Platform SWT component
developers list." <platform-swt-dev@xxxxxxxxxxx>, platform-swt-dev-bounces@xxxxxxxxxxx
|
Subject
| Re: [platform-swt-dev] SWT_AWT and Accessibility |
|
Hi Richard,
Thats very interesting news..
So if im understanding correctly.. because swing would use the java access
bridge and swt uses an alternative method.. it basically confuses any AT
application interogating the app.
Two implementations at the same time is generally not supported?
If so this would leave my development team with only really one option..
change our swing panels to swt composites to gain AT support.
Can you confirm that i have understood this correctly.
Thanks,
Jamie M. Guillemette
IT Solutions Developer
TD Enterprise Technology Solutions
275 Dundas Street, 11th Floor, London
(519) 663-1952
Steve
Northover
<Steve_Nort
To
hover@xxxxx
"Eclipse Platform SWT component
m.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/09/2007
05:28 PM
Please
respond to
"Eclipse
Platform
SWT
component
developers
list."
<platform-s
wt-dev@ecli
pse.org>
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:
To
platform-swt-dev-bounces@ecli
"Eclipse Platform SWT component
pse.org
developers list."
<platform-swt-dev@xxxxxxxxxxx>
cc
05/09/2007 04:41 PM
"Eclipse Platform SWT component
developers list."
<platform-swt-dev@xxxxxxxxxxx>,
Please respond to
platform-swt-dev-bounces@eclips
"Eclipse Platform SWT
e.org
component developers list."
Subject
<platform-swt-dev@xxxxxxxxxx
Re: [platform-swt-dev] SWT_AWT
g>
and
Accessibility
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: pic12592.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
pic25181.gif)
To
05/09/2007 03:18 PM
(Embedded image moved to file:
pic05014.gif)
"Eclipse Platform SWT
Please respond to
component developers list."
"Eclipse Platform SWT component
<platform-swt-dev@xxxxxxxxxxx>
developers list."
(Embedded image moved to file:
<platform-swt-dev@xxxxxxxxxxx> pic10407.gif)
cc
(Embedded image moved to file:
pic12316.gif)
(Embedded image
moved to file:
pic23544.gif)
Subject
(Embedded image moved to file:
pic18901.gif)
Re: [platform-swt-dev] SWT_AWT
and Accessibility
(Embedded image
moved to file:
pic31617.gif)
(
E
m
b
e
d
d
e
d
i
m
a
g
e
m
o
v
e
d
t
o
f
i
l
e
:
p
i
c
0
3
7
0
4
.
g
i
f
)
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@ecl
05/09/2007 04:10 PM
ipse.org
cc
(Embedded image
moved to file:
Please respond to
pic13069.gif)
"Eclipse Platform SWT component developers
Subject
list." <platform-swt-dev@xxxxxxxxxxx>
[platform-swt-dev]
SWT_AWT and
Accessibility
(Embedded image moved to
file: pic14949.gif)
(Embedded image moved to
file: pic17387.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: pic11232.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
Attachment:
pic12592.gif
Description: GIF image
Attachment:
pic25181.gif
Description: GIF image
Attachment:
pic05014.gif
Description: GIF image
Attachment:
pic10407.gif
Description: GIF image
Attachment:
pic12316.gif
Description: GIF image
Attachment:
pic23544.gif
Description: GIF image
Attachment:
pic18901.gif
Description: GIF image
Attachment:
pic31617.gif
Description: GIF image
Attachment:
pic03704.gif
Description: GIF image
Attachment:
pic13069.gif
Description: GIF image
Attachment:
pic14949.gif
Description: GIF image
Attachment:
pic17387.gif
Description: GIF image
Attachment:
pic11232.gif
Description: GIF image