WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: JAWS 18 "no more headings at level X in this section"

for

From: Joseph Sherman
Date: Apr 14, 2017 9:16AM


Great explanation, thanks.

Joseph


> -----Original Message-----
> From: WebAIM-Forum [mailto: <EMAIL REMOVED> ] On Behalf
> Of Birkir R. Gunnarsson
> Sent: Friday, April 14, 2017 11:11 AM
> To: WebAIM Discussion List < <EMAIL REMOVED> >
> Subject: Re: [WebAIM] JAWS 18 "no more headings at level X in this section"
>
> This stems from the special way in which Jaws handles heading structure.
> Jaws will stop looking for your desired level heading either if it hits the end of the
> page or if it hits a heading at a lower level.
> In other words:
> If you have the following heading structure:
>
> h2 - welcome
>
> h3 heading in header
>
> h1 main content
>
> h2 search results
>
> h3 search result 1
>
> h3 search result 2
>
> Imagine you are on the h2 heading at the top of the page and press "3", you will be
> taken to the h3 heading in the header.
> Now pressing any number other than 1 will cause Jaws to announce "no more
> headings in this section", because the next heading is an h1.
> Jaws is correct in a way, if we use heading structure to mark sections.
>
>
> If you press "1" at this point, you are placed on the "h1" heading.
>
> If you press "3" with focus on the h1 heading, you will get a "no more headings in
> this section" announcement again, because Jaws started looking, found an "h2"
> (search results" and stopped.
>
> If you press "2" you move to search results.
> If you now press "3" you can move between search results.
>
> If you want the fastest way to get from top of this page to search results using
> heading navigation in Jaws you have to press "1" "2" and then "3" (main, search
> results, individual result).
>
> NVDA does not not split the page into sections, it just looks for the next h3 heading
> on the page regardless of context.
>
> I am not sure if you can change Jaws settings to behave that way.
> Oddly, I like the Jaws's approach (maybe it is habit).
>
>
>
> On 4/14/17, Steve Faulkner < <EMAIL REMOVED> > wrote:
> > Hi Joseph,
> >
> > it would be helpful if you provided:
> >
> > - JAWS version
> > - browser and version
> > - code example
> >
> >
> > --
> >
> > Regards
> >
> > SteveF
> > Current Standards Work @W3C
> > <http://www.paciellogroup.com/blog/2015/03/current-standards-work-at-w
> > 3c/>
> >
> > On 14 April 2017 at 15:06, Joseph Sherman < <EMAIL REMOVED> >
> wrote:
> >
> >> I'm on a page with a bunch of regions and headings. The top of page
> >> is the banner and search region. The main region has search results
> >> which are labeled H3. When the page loads the cursor is at the top of
> >> the page in the banner region. I press "3" to go to the first h3
> >> search results, but JAWS says ""no more headings at level X in this
> >> section".
> >> Why does JAWS give this unhelpful response instead of going to the h3
> >> in the Main section? When I press "3' in NVDA, it goes directly to
> >> the first search result, h3.
> >>
> >> I find this happens in a number of pages and web applications and is
> >> very annoying to have to first be in the correct region, and then be
> >> able to go to the heading that I want. Sometimes this happens for h1
> >> in the main region if I am in the banner region. Is there a setting
> >> or something I can change in JAWS?
> >> Joseph
> >>
> >> > >> > >> archives at http://webaim.org/discussion/archives
> >> > >>
> > > > > > archives at http://webaim.org/discussion/archives
> > > >
>
>
> --
> Work hard. Have fun. Make history.
> > > http://webaim.org/discussion/archives
>