E-mail List Archives

Search E-mail List Archives for

Number of posts in this thread: 5 (In chronological order)

From: Hoffman, Allen
Date: Tue, Jan 26 2010 3:21PM
Subject: Java AccessBridge, JAWS, Magic, ZoomText, NVDA
No previous message | Next message →

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.

From: Don Mauck
Date: Tue, Jan 26 2010 4:00PM
Subject: Re: Java AccessBridge, JAWS, Magic, ZoomText, NVDA
← Previous message | Next message →

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 ADDRESS 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.

From: Tim Harshbarger
Date: Wed, Jan 27 2010 7:27AM
Subject: Re: Java AccessBridge, JAWS, Magic, ZoomText, NVDA
← Previous message | Next message →

Allen,
You may want to double check the installation of the java access bridge (jab.) We have had a couple instances where we discovered that another JRE had been installed after we had installed the jab and the java app was using the newer JRE install.
The only other suggestion I can think of that might help is to try to use java ferret or java monkey to check the java app. That might give you an idea of what accessibility information is being exposed by the java app.
I think that both ZoomText and NVDA do support the java access bridge. If that is the case, their use of it should be similar to JAWS. At least, I haven't come across anything to make me think that JAWS gets its information about the java app from anywhere else besides the java access bridge--I mean for Swing UI components.

Thanks,
Tim

-----Original Message-----
From: = EMAIL ADDRESS REMOVED = [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Hoffman, Allen
Sent: Tuesday, January 26, 2010 4: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.

From: Moore,Michael (DARS)
Date: Wed, Jan 27 2010 9:00AM
Subject: Re: Java AccessBridge, JAWS, Magic, ZoomText, NVDA
← Previous message | Next message →

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 ADDRESS REMOVED = [mailto: = EMAIL ADDRESS 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 ADDRESS 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.

From: November Samnee
Date: Wed, Jan 27 2010 9:21AM
Subject: Re: Java AccessBridge, JAWS, Magic, ZoomText, NVDA
← Previous message | No next message

Mike -

I find it very interesting that ZoomText looks for the title attribute
instead of using the label element. Do you (or anyone else for that matter)
know of some good sources for that sort of information about ZoomText?

November Samnee



On Wed, Jan 27, 2010 at 10:01 AM, Moore,Michael (DARS) <
= EMAIL ADDRESS REMOVED = > wrote:

> 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 ADDRESS REMOVED = [mailto:
> = EMAIL ADDRESS 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 ADDRESS 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.
>
>
>
>
>