WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: JAWS 10 and Hidden Text

for

From: Terrill Thompson
Date: Mar 23, 2009 3:55PM

Hi Randi,

You're correct - I expected Test 1 (using visibility:hidden) and Test 2
(using display:none) to both be hidden visibly, as well as hidden to screen
reader users. Test 3 is hidden by positioning text off screen, which has
become a widely accepted means of hiding content visibly that you want
screen readers to read.

My initial concern when I saw the JAWS "bug fix" was that they might have
"fixed" the off-screen positioning solution. Fortunately that's not the
case.

Jared correctly pointed out that the JAWS fix applies to a bug documented in
a Juicy Studio article, where JAWS was erroneously reading content hidden
using display:none, but only under certain very specific circumstances (only
on span elements nested within anchor tags).

Terry

> -----Original Message-----
> From: <EMAIL REMOVED> [mailto:webaim-forum-
> <EMAIL REMOVED> ] On Behalf Of Randi
> Sent: Monday, March 23, 2009 1:43 PM
> To: WebAIM Discussion List
> Subject: Re: [WebAIM] JAWS 10 and Hidden Text
>
> Hi there. I'm just curious if Test 1 and Test 2 were supposed to show
> anything or not? Because using Voiceover there was nothing under those
> headings after the description. Test 3 worked just fine.
>
> Was that what you are trying to see? Because if there's supposed to be
> content there for the first 2 tests, then Voiceover did not read it.
>
> Thanks,
> Randi
>
> On 3/23/09, Jared Smith < <EMAIL REMOVED> > wrote:
> > I believe they may have addressed the instances outlined here -
> > http://juicystudio.com/article/screen-readers-display-none.php -
> where
> > content hidden with display:none was being read by JAWS.
> >
> > If this is indeed the case, then this is a very good thing as content
> > that is truly hidden with CSS should never be identified by screen
> > readers.
> >
> > Jared Smith
> > WebAIM
> >