E-mail List Archives

Search E-mail List Archives for

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

From: Jennison Mark Asuncion
Date: Fri, Mar 05 2010 6:48AM
Subject: jaws, firefox, & display:none & display:block
No previous message | Next message →

Hello,

Wondering if anyone is experiencing this issue in Firefox (3.5), using
JAWS (10.1154) -a page has been coded in such a way that display:none is
used to first hide text on a page when it first loads. When a button is
triggered, it shows the text using display:block. The idea is when the
user clicks OK, that text hides once again using display:none. With JAWS
in IE, the behavior is the same visually and with JAWS in that on page
load, JAWS does not speak the hidden text, it speaks it when a button is
triggered, and it stops recognizing and speaking the text once the user
clicks the OK button. In Firefox however, JAWS still recognizes and reads
the text once the OK button is pressed, even though it is hidden. The only
way to get JAWS not to continue speaking the hidden text is to do an
insert+escape.

Is this expected behavior with JAWS in Firefox when implementing
display:none and display:block? Is there a work-around? If it is a bug,
does this clear up in later versions of JAWS?

Jennison

Jennison Asuncion
Co-Director, Adaptech Research Network http://www.adaptech.org
LinkedIn at http://www.linkedin.com/in/jennison

From: E.J. Zufelt
Date: Fri, Mar 05 2010 6:51AM
Subject: Re: jaws, firefox, & display:none & display:block
← Previous message | Next message →

Good morning,

To the best of my knowledge this is a JAWS bug that I believe has been corrected in JAWS 11.

Thanks,
Everett Zufelt
http://zufelt.ca

Follow me on Twitter
http://twitter.com/ezufelt

View my LinkedIn Profile
http://www.linkedin.com/in/ezufelt



On 2010-03-05, at 7:49 AM, Jennison Mark Asuncion wrote:

> Hello,
>
> Wondering if anyone is experiencing this issue in Firefox (3.5), using
> JAWS (10.1154) -a page has been coded in such a way that display:none is
> used to first hide text on a page when it first loads. When a button is
> triggered, it shows the text using display:block. The idea is when the
> user clicks OK, that text hides once again using display:none. With JAWS
> in IE, the behavior is the same visually and with JAWS in that on page
> load, JAWS does not speak the hidden text, it speaks it when a button is
> triggered, and it stops recognizing and speaking the text once the user
> clicks the OK button. In Firefox however, JAWS still recognizes and reads
> the text once the OK button is pressed, even though it is hidden. The only
> way to get JAWS not to continue speaking the hidden text is to do an
> insert+escape.
>
> Is this expected behavior with JAWS in Firefox when implementing
> display:none and display:block? Is there a work-around? If it is a bug,
> does this clear up in later versions of JAWS?
>
> Jennison
>
> Jennison Asuncion
> Co-Director, Adaptech Research Network http://www.adaptech.org
> LinkedIn at http://www.linkedin.com/in/jennison
>

From: Pratik Patel
Date: Fri, Mar 05 2010 7:09AM
Subject: Re: jaws, firefox, & display:none & display:block
← Previous message | Next message →

Hello,

Jennison Mark Asuncion wrote:


Is this expected behavior with JAWS in Firefox when implementing
display:none and display:block? Is there a work-around? If it is a bug,
does this clear up in later versions of JAWS?

P: This is indeed a bug in JAWS that has been reported several times since
JAWS 10.x. This was first noticed with Firefox 2. I'm afraid JAWS 11 does
nothing to solve this issue. If anyone else has a different experience, I'd
love to see an example. There are several times when JAWS+escape has to be
used to ensure that the virtual buffer is refreshed-that JAWS realizes that
the buffer is refreshed to be more precise. Overall though, Firefox
provides a far superior experience with Ajaxy sites with JAWS than does IE.
See facebook and Gmail as examples. I have recently encountered some
strange sites -especially those developed with asp.net -that behave better
with JAWS 10 and 9 and IE 7 and 8 and Firefox 3.5. There seems to be some
regression in JAWS 11. But, as you know, I have quite a few issues with
JAWS 11; I may not be the most objective voice when it comes to this
particular gem from Freedomscientific.

Pratik

From: E.J. Zufelt
Date: Fri, Mar 05 2010 7:33AM
Subject: Re: jaws, firefox, & display:none & display:block
← Previous message | No next message

Good morning,

After reading Pratik's message I went back and tested this behaviour. I thought that it had been corrected in JAWS 11, but clearly not in all situations. A good place to test this functionality is on the jQury hide() API page at http://api.jquery.com/hide/

There are a lot of headings on this page, multiple headings contain the text "Demo". The fourth heading which contains the text "Demo" is a demo of the functionality with two buttons, one labeled Hide and one labeled Show. After activating Hide I had to refresh the virtual buffer to get the paragraph of text which comes after the buttons to be hidden in the JAWS virtual buffer.

HTH,
Everett Zufelt
http://zufelt.ca

Follow me on Twitter
http://twitter.com/ezufelt

View my LinkedIn Profile
http://www.linkedin.com/in/ezufelt



On 2010-03-05, at 8:10 AM, Pratik Patel wrote:

> Hello,
>
> Jennison Mark Asuncion wrote:
>
>
> Is this expected behavior with JAWS in Firefox when implementing
> display:none and display:block? Is there a work-around? If it is a bug,
> does this clear up in later versions of JAWS?
>
> P: This is indeed a bug in JAWS that has been reported several times since
> JAWS 10.x. This was first noticed with Firefox 2. I'm afraid JAWS 11 does
> nothing to solve this issue. If anyone else has a different experience, I'd
> love to see an example. There are several times when JAWS+escape has to be
> used to ensure that the virtual buffer is refreshed-that JAWS realizes that
> the buffer is refreshed to be more precise. Overall though, Firefox
> provides a far superior experience with Ajaxy sites with JAWS than does IE.
> See facebook and Gmail as examples. I have recently encountered some
> strange sites -especially those developed with asp.net -that behave better
> with JAWS 10 and 9 and IE 7 and 8 and Firefox 3.5. There seems to be some
> regression in JAWS 11. But, as you know, I have quite a few issues with
> JAWS 11; I may not be the most objective voice when it comes to this
> particular gem from Freedomscientific.
>
> Pratik
>
>
>