WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: JAWS Accordion test


From: Al Sparber
Date: Mar 23, 2009 9:40AM

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 professional
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 to
read one line at a time?

Al Sparber - PVII

----- Original Message -----
From: "Priti Rohra" < <EMAIL REMOVED> >

> Hi Al,
> Well I have a totally different idea, why not let it work the same way for
> screen reader users as it does for sighted individuals.
> JAWS does identify it as "same page link", let users click on the link and
> 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 will
> have no option to skip pass to the current menu and access the next one...