WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: JAWS Accordion test


From: Patrick Burke
Date: Mar 23, 2009 11:10AM

Hi Randall,

With Jaws 10 & IE7 (with braille display), I don't notice any effect
from Al's test page at all. That is, Jaws reads the whole content of
the page, including the Nursery Rhyme & Astronomer paragraphs.
Triggering the links associated with the paragraphs makes no change.

(We have done other Javascript tests where you can use links to make
paragraphs appear & disappear. But I don't think that was Al's intent
with this one.)


At 09:45 AM 3/23/2009, Randall Pope wrote:
>Hi All,
>For those who are using screen reader, can you give me your insight in the
>JAWS Accordion test, while using a refreshing braille display on computers,
>and notetakers such as BrailleNote? I have deafblind people who cannot hear
>but depend on braille to read the content. Many thanks.
>With Warm Regards,
>Randall "Randy" Pope
>American Association of the Deaf-Blind
>Website: http://www.aadb.org
>301 495-4402 VP/TTY
>301 495-4403 Voice
>301 495-4404 Fax
>Want to keep up with the latest news in the Deaf-Blind Community? Consider
>subscribing to the monthly newsletter, "AADB Today" at http://aadb.org. It's
>free and AADB membership is not required.
>-----Original Message-----
>[mailto: <EMAIL REMOVED> ] On Behalf Of Randi
>Sent: Monday, March 23, 2009 12:25 PM
>To: WebAIM Discussion List
>Subject: Re: [WebAIM] JAWS Accordion test
>On the accordian menus, I'm a complete novice so bear with me. I heard
>the link but did not click because I assume, just by thinking of an
>accordian, that once my curser passes over the link, the content
>opens, and thats where I read the nursery rhyme. Do I have that
>correct? I knew what I was trying to test though, so If I didn't know
>it was an ccordian menu and I clicked on the link and nothing
>happened, I'd just arrow down farther and then discover the text. This
>happens quite often on some pages. If I click a link and nothing
>happens, I assume its some fancy programming and arrow down further.
>As for skip to content links, I'm having no luck with those. I don't
>know if itsa a Voiceover thing so I've actually got a question out to
>my Apple guru with regards to these. These links never do anything.
>As far as the question about Jaws reading a whole page, In Voiceover I
>have that option if I want, but I never use it. I prefer to go find
>stuff on my own. As for right now, I just arrow through pages. I
>haven't mastered navigation by header yet. On pages I'm familiar with,
>this is not a problem. Voicover gives me blips and blurps when it goes
>past lines and paragraphs, so I just have those sounds memorized so I
>know how far to arrow down. I don't know if that helps, but thats how
>I've been doing it. I need to learn header navigation though, as I'm
>sure it will speed things up.
>Thanks for including me in this one. Most of your discussions go right
>over my head so I like ones I understand hehe.
>On 3/23/09, Steve Green < <EMAIL REMOVED> > wrote:
> > In my experience they read one line at a time, although they may use other
> > strategies in addition, such as using the links list, heading list or
> > jumping to headings.
> >
> > 'SayAll' mode, which is the mode where JAWS reads continuously, is not
> > particularly useful for most tasks because the semantic structure is not
> > read out in this mode and it is impossible to build a mental model of the
> > page. It is really only useful for reading large blocks of text, but even
> > then I have not seen anyone use it.
> >
> > To a large extent I expect it depends how the user was trained, and maybe
> > someone who has not received any training may tend to use it more because
> > JAWS switches to SayAll mode each time a new page loads.
> >
> > Steve
> >
> >
> >
> > -----Original Message-----
> > [mailto: <EMAIL REMOVED> ] On Behalf Of Al Sparber
> > Sent: 23 March 2009 15:38
> > To: WebAIM Discussion List
> > Subject: Re: [WebAIM] JAWS Accordion test
> >
> > If it were a widget that could only be used as a menu, I'd agree
> > unequivocally. However, the dominant use for an accordion widget is as a
> > means to visually compress content. So the objective was to uncompress
> > things for assistive reader users to a normal page-state. If deployed as a
> > menu, or as a hybrid with content and link lists, then a designer could
> > introduce skip and skip-to links in appropriate spots.
> >
> > I have another question (perhaps Randi can weigh in, too). As a
> > in the field, how do most JAWS users prefer to listen to a page? On the
> > first pass, for instance, do they simply let JAWS recite what it can
> > contiguously--or, do they tend to stop JAWS and use their navigation keys
> > read one line at a time?
> >
> > --
> > Al Sparber - PVII
> > http://www.projectseven.com
> >
> >
> >
> >
> > ----- Original Message -----
> > From: "Priti Rohra" < <EMAIL REMOVED> >
> >
> >> Hi Al,
> >>
> >> Well I have a totally different idea, why not let it work the same way
> >> screen reader users as it does for sighted individuals.
> >> JAWS does identify it as "same page link", let users click on the link
> >> read the information thus displayed rather then making it available as
> >> expanded menu in the first place.
> >>
> >> This will avoid the confusion and the content will function uniformly for
> >> all users. Currently it is making the information available to screen
> >> reader
> >> users irrespective of the user's decision to click on the link.
> >>
> >> I don't agree with the opinion of setting the href value to empty.
> >> Consider a situation, where in accordion menus are used to present
> >> drop-down
> >> menus for a website navigation, and all the sub-menus are read out for
> >> screen reader users. How usable will it for screen reader users? They
> >> have no option to skip pass to the current menu and access the next
> >

Patrick J. Burke

UCLA Disabilities &
Computing Program

Phone: 310 206-6004
E-mail: burke <at> ucla. edu