E-mail List Archives

Re: Java AccessBridge, JAWS, Magic, ZoomText, NVDA

for

From: Moore,Michael (DARS)
Date: Jan 27, 2010 9:00AM


The reader in ZoomText has a lot of quirks, and does not support common web standards for accessibility. For example it does not support the label element, and gets its label information from the title attribute in the input instead.

That being said, we have had very bad luck with the JAVA access bridge. We have had vastly different performance between systems with JAWS and the Access Bridge installed and have been unable to get the interactive elements to report or perform reliably when using a screen reader.

Mike Moore
(512) 424-4159


-----Original Message-----
From: <EMAIL REMOVED> [mailto: <EMAIL REMOVED> ] On Behalf Of Don Mauck
Sent: Tuesday, January 26, 2010 5:00 PM
To: WebAIM Discussion List
Subject: Re: [WebAIM] Java AccessBridge, JAWS, Magic, ZoomText, NVDA

Removing the JAWS video intercept drivers will cause a lot of other problems with JAWS itself. I don't think that the Access bridge product was ever meant for Zoom Text.

-----Original Message-----
From: Hoffman, Allen [mailto: <EMAIL REMOVED> ]
Sent: Tuesday, January 26, 2010 3:21 PM
To: WebAIM Discussion List
Subject: [WebAIM] Java AccessBridge, JAWS, Magic, ZoomText, NVDA

Without naming names to protect the guilty, I have the following
situation.

An online course is accessible with JAWS and Magic via the Java
AccessBridge. However, "text" field data is not read using either
ZoomText or NVDA, even when configured correctly for the AccessBridge.
What gives? Does NVDA have a missing component supporting the
AccessBridge, does ZoomText? Are there multiple methods that can be
used to deliver text field values via the Bridge, and some AT supports
more than others, or does JAWS use something additional to greab the
information-e.g. display driver data? Anyone who has a similar example
of such behavior and found the specific answer? If so please post.

Will have to try JAWS minus video intercept and see what happens.