E-mail List Archives

Search E-mail List Archives for

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

From: Marco Maertens
Date: Tue, May 18 2010 12:36PM
Subject: JAWS, Firefox, display: none, input tag
No previous message | Next message →

Hi,

We're having a interesting, but frustrating problem, involving Firefox 3.6, JAWS 11, and UI Tabs.

We have an interface with several tabs, which are hidden and displayed using JavaScript (UI Tabs). Each tab is hidden using display: none CSS and redisplayed using the display:block CSS. Pretty straightforward.

However, if you display the first tab, then display any other tab, then return to the first tab, JAWS will not read out the currently selected (first) tab. Instead, it will read out the previously displayed (but now hidden) tab. And the weird thing is that this only happens is when the content of that tab happens to contain a text input tag. As soon as that input tag is removed, JAWS reads out the tabs exactly as they display on the screen. Other types of input tags, such as checkboxes, do not cause the same odd behavior.

This happens in Firefox but not in IE.

Has anyone seen this or have any idea what's going on? More importantly, is there any fix or workaround?

Thanks in advance for your help,
-Marco.

Marco Maertens
Empathy Lab

From: James Nurthen
Date: Tue, May 18 2010 1:30PM
Subject: Re: JAWS, Firefox, display: none, input tag
← Previous message | Next message →

Marco,
Do you have the latest version of JAWS11 (11.0.1430)? It was our
experience that there were a whole bunch of buffer synchronization
issues in previous JAWS 11 releases which seem to have improved
considerably in the latest version.
Regards,
James

On 18 May 2010 10:38, Marco Maertens < = EMAIL ADDRESS REMOVED = > wrote:
> Hi,
>
> We're having a interesting, but frustrating problem, involving Firefox 3.6, JAWS 11, and UI Tabs.
>
> We have an interface with several tabs, which are hidden and displayed using JavaScript (UI Tabs). Each tab is hidden using display: none CSS and redisplayed using the display:block CSS. Pretty straightforward.
>
> However, if you display the first tab, then display any other tab, then return to the first tab, JAWS will not read out the currently selected (first) tab. Instead, it will read out the previously displayed (but now hidden) tab. And the weird thing is that this only happens is when the content of that tab happens to contain a text input tag. As soon as that input tag is removed, JAWS reads out the tabs exactly as they display on the screen. Other types of input tags, such as checkboxes, do not cause the same odd behavior.
>
> This happens in Firefox but not in IE.
>
> Has anyone seen this or have any idea what's going on? More importantly, is there any fix or workaround?
>
> Thanks in advance for your help,
> -Marco.
>
> Marco Maertens
> Empathy Lab
>
>

From: Marco Maertens
Date: Tue, May 18 2010 1:57PM
Subject: Re: JAWS, Firefox, display: none, input tag
← Previous message | Next message →

Hi James,

It looks like we're running 11.0.756U. I thought we were running the latest version, but apparently not. I'll give that a shot. Do you know how recently 1430 came out?

-Marco.

Marco Maertens
Empathy Lab

-----Original Message-----
From: = EMAIL ADDRESS REMOVED = [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of James Nurthen
Sent: Tuesday, May 18, 2010 2:32 PM
To: WebAIM Discussion List
Subject: Re: [WebAIM] JAWS, Firefox, display: none, input tag

Marco,
Do you have the latest version of JAWS11 (11.0.1430)? It was our
experience that there were a whole bunch of buffer synchronization
issues in previous JAWS 11 releases which seem to have improved
considerably in the latest version.
Regards,
James

On 18 May 2010 10:38, Marco Maertens < = EMAIL ADDRESS REMOVED = > wrote:
> Hi,
>
> We're having a interesting, but frustrating problem, involving Firefox 3.6, JAWS 11, and UI Tabs.
>
> We have an interface with several tabs, which are hidden and displayed using JavaScript (UI Tabs). Each tab is hidden using display: none CSS and redisplayed using the display:block CSS. Pretty straightforward.
>
> However, if you display the first tab, then display any other tab, then return to the first tab, JAWS will not read out the currently selected (first) tab. Instead, it will read out the previously displayed (but now hidden) tab. And the weird thing is that this only happens is when the content of that tab happens to contain a text input tag. As soon as that input tag is removed, JAWS reads out the tabs exactly as they display on the screen. Other types of input tags, such as checkboxes, do not cause the same odd behavior.
>
> This happens in Firefox but not in IE.
>
> Has anyone seen this or have any idea what's going on? More importantly, is there any fix or workaround?
>
> Thanks in advance for your help,
> -Marco.
>
> Marco Maertens
> Empathy Lab
>
>

From: James Nurthen
Date: Tue, May 18 2010 2:36PM
Subject: Re: JAWS, Firefox, display: none, input tag
← Previous message | Next message →

Mid April

Regards,
James

On 18 May 2010 11:57, Marco Maertens < = EMAIL ADDRESS REMOVED = > wrote:
> Hi James,
>
> It looks like we're running 11.0.756U. I thought we were running the latest version, but apparently not. I'll give that a shot. Do you know how recently 1430 came out?
>
> -Marco.
>
> Marco Maertens
> Empathy Lab
>
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED = [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of James Nurthen
> Sent: Tuesday, May 18, 2010 2:32 PM
> To: WebAIM Discussion List
> Subject: Re: [WebAIM] JAWS, Firefox, display: none, input tag
>
> Marco,
> Do you have the latest version of JAWS11 (11.0.1430)? It was our
> experience that there were a whole bunch of buffer synchronization
> issues in previous JAWS 11 releases which seem to have improved
> considerably in the latest version.
> Regards,
> James
>
> On 18 May 2010 10:38, Marco Maertens < = EMAIL ADDRESS REMOVED = > wrote:
>> Hi,
>>
>> We're having a interesting, but frustrating problem, involving Firefox 3.6, JAWS 11, and UI Tabs.
>>
>> We have an interface with several tabs, which are hidden and displayed using JavaScript (UI Tabs). Each tab is hidden using display: none CSS and redisplayed using the display:block CSS. Pretty straightforward.
>>
>> However, if you display the first tab, then display any other tab, then return to the first tab, JAWS will not read out the currently selected (first) tab. Instead, it will read out the previously displayed (but now hidden) tab. And the weird thing is that this only happens is when the content of that tab happens to contain a text input tag. As soon as that input tag is removed, JAWS reads out the tabs exactly as they display on the screen. Other types of input tags, such as checkboxes, do not cause the same odd behavior.
>>
>> This happens in Firefox but not in IE.
>>
>> Has anyone seen this or have any idea what's going on? More importantly, is there any fix or workaround?
>>
>> Thanks in advance for your help,
>> -Marco.
>>
>> Marco Maertens
>> Empathy Lab
>>
>>

From: David Farough
Date: Tue, May 18 2010 3:00PM
Subject: Re: JAWS, Firefox, display: none, input tag
← Previous message | Next message →

The latest release of jaws is Jaws 11.0.1447 this came out in May.
I did not see any mention of scripting updates for Firefox in the
release.

David Farough
Application Accessibility Coordinator/coordonateur de l'accessibilité
Information Technology Services Directorate /
Direction des services d'information technologiques
Public Service Commission / Commission de la fonction publique
Email / Courriel: = EMAIL ADDRESS REMOVED =
Tel. / Tél: (613) 992-2779

>>> James Nurthen < = EMAIL ADDRESS REMOVED = > 03:36 PM Tuesday, May 18, 2010
>>>
Mid April

Regards,
James

On 18 May 2010 11:57, Marco Maertens < = EMAIL ADDRESS REMOVED = > wrote:
> Hi James,
>
> It looks like we're running 11.0.756U. I thought we were running the
latest version, but apparently not. I'll give that a shot. Do you know
how recently 1430 came out?
>
> -Marco.
>
> Marco Maertens
> Empathy Lab
>
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of James
Nurthen
> Sent: Tuesday, May 18, 2010 2:32 PM
> To: WebAIM Discussion List
> Subject: Re: [WebAIM] JAWS, Firefox, display: none, input tag
>
> Marco,
> Do you have the latest version of JAWS11 (11.0.1430)? It was our
> experience that there were a whole bunch of buffer synchronization
> issues in previous JAWS 11 releases which seem to have improved
> considerably in the latest version.
> Regards,
> James
>
> On 18 May 2010 10:38, Marco Maertens < = EMAIL ADDRESS REMOVED = >
wrote:
>> Hi,
>>
>> We're having a interesting, but frustrating problem, involving
Firefox 3.6, JAWS 11, and UI Tabs.
>>
>> We have an interface with several tabs, which are hidden and
displayed using JavaScript (UI Tabs). Each tab is hidden using display:
none CSS and redisplayed using the display:block CSS. Pretty
straightforward.
>>
>> However, if you display the first tab, then display any other tab,
then return to the first tab, JAWS will not read out the currently
selected (first) tab. Instead, it will read out the previously displayed
(but now hidden) tab. And the weird thing is that this only happens is
when the content of that tab happens to contain a text input tag. As
soon as that input tag is removed, JAWS reads out the tabs exactly as
they display on the screen. Other types of input tags, such as
checkboxes, do not cause the same odd behavior.
>>
>> This happens in Firefox but not in IE.
>>
>> Has anyone seen this or have any idea what's going on? More
importantly, is there any fix or workaround?
>>
>> Thanks in advance for your help,
>> -Marco.
>>
>> Marco Maertens
>> Empathy Lab
>>
>>

From: Marco Maertens
Date: Wed, May 19 2010 11:39AM
Subject: Re: JAWS, Firefox, display: none, input tag
← Previous message | No next message

Hi,

Even with the 11.0.1447 we're still seeing the same behavior.

We found a hack that seems to get around the problem. If we remove the input tag dynamically using DOM scripting, set the focus to the contents, and then re-insert the input tag with DOM scripting, it behaves as expected.

This is very kludgy, to say the least, especially since we're handing over the pages to another firm for back-end integration. I'm afraid the solution will not survive the return trip.

Anyone familiar with this?

-Marco.

Marco Maertens
Empathy Lab

-----Original Message-----
From: = EMAIL ADDRESS REMOVED = [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of David Farough
Sent: Tuesday, May 18, 2010 4:02 PM
To: WebAIM Discussion List
Subject: Re: [WebAIM] JAWS, Firefox, display: none, input tag

The latest release of jaws is Jaws 11.0.1447 this came out in May.
I did not see any mention of scripting updates for Firefox in the
release.

David Farough
Application Accessibility Coordinator/coordonateur de l'accessibilité
Information Technology Services Directorate /
Direction des services d'information technologiques
Public Service Commission / Commission de la fonction publique
Email / Courriel: = EMAIL ADDRESS REMOVED =
Tel. / Tél: (613) 992-2779

>>> James Nurthen < = EMAIL ADDRESS REMOVED = > 03:36 PM Tuesday, May 18, 2010
>>>
Mid April

Regards,
James

On 18 May 2010 11:57, Marco Maertens < = EMAIL ADDRESS REMOVED = > wrote:
> Hi James,
>
> It looks like we're running 11.0.756U. I thought we were running the
latest version, but apparently not. I'll give that a shot. Do you know
how recently 1430 came out?
>
> -Marco.
>
> Marco Maertens
> Empathy Lab
>
> -----Original Message-----
> From: = EMAIL ADDRESS REMOVED =
[mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of James
Nurthen
> Sent: Tuesday, May 18, 2010 2:32 PM
> To: WebAIM Discussion List
> Subject: Re: [WebAIM] JAWS, Firefox, display: none, input tag
>
> Marco,
> Do you have the latest version of JAWS11 (11.0.1430)? It was our
> experience that there were a whole bunch of buffer synchronization
> issues in previous JAWS 11 releases which seem to have improved
> considerably in the latest version.
> Regards,
> James
>
> On 18 May 2010 10:38, Marco Maertens < = EMAIL ADDRESS REMOVED = >
wrote:
>> Hi,
>>
>> We're having a interesting, but frustrating problem, involving
Firefox 3.6, JAWS 11, and UI Tabs.
>>
>> We have an interface with several tabs, which are hidden and
displayed using JavaScript (UI Tabs). Each tab is hidden using display:
none CSS and redisplayed using the display:block CSS. Pretty
straightforward.
>>
>> However, if you display the first tab, then display any other tab,
then return to the first tab, JAWS will not read out the currently
selected (first) tab. Instead, it will read out the previously displayed
(but now hidden) tab. And the weird thing is that this only happens is
when the content of that tab happens to contain a text input tag. As
soon as that input tag is removed, JAWS reads out the tabs exactly as
they display on the screen. Other types of input tags, such as
checkboxes, do not cause the same odd behavior.
>>
>> This happens in Firefox but not in IE.
>>
>> Has anyone seen this or have any idea what's going on? More
importantly, is there any fix or workaround?
>>
>> Thanks in advance for your help,
>> -Marco.
>>
>> Marco Maertens
>> Empathy Lab
>>
>>