E-mail List Archives
Thread: JAWS 18 "no more headings at level X in this section"
Number of posts in this thread: 8 (In chronological order)
From: Joseph Sherman
Date: Fri, Apr 14 2017 8:06AM
Subject: JAWS 18 "no more headings at level X in this section"
No previous message | Next message →
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
From: Steve Faulkner
Date: Fri, Apr 14 2017 8:30AM
Subject: Re: JAWS 18 "no more headings at level X in this section"
← Previous message | Next message →
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-w3c/>;
On 14 April 2017 at 15:06, Joseph Sherman < = EMAIL ADDRESS 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
>
> > > > >
From: Birkir R. Gunnarsson
Date: Fri, Apr 14 2017 9:11AM
Subject: Re: JAWS 18 "no more headings at level X in this section"
← Previous message | Next message →
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 ADDRESS 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-w3c/>;
>
> On 14 April 2017 at 15:06, Joseph Sherman < = EMAIL ADDRESS 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
>>
>> >> >> >> >>
> > > > >
--
Work hard. Have fun. Make history.
From: Joseph Sherman
Date: Fri, Apr 14 2017 9:16AM
Subject: Re: JAWS 18 "no more headings at level X in this section"
← Previous message | Next message →
Great explanation, thanks.
Joseph
> -----Original Message-----
> From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf
> Of Birkir R. Gunnarsson
> Sent: Friday, April 14, 2017 11:11 AM
> To: WebAIM Discussion List < = EMAIL ADDRESS 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 ADDRESS 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 ADDRESS 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
>
From: Andrews, David B (DEED)
Date: Fri, Apr 14 2017 10:37AM
Subject: Re: JAWS 18 "no more headings at level X in this section"
← Previous message | Next message →
I like the JAWS approach too, it gives you a little more idea of page organization by staying within a section. You can also use the h or shift-h commands to move to the next, or previous heading, whatever level it is at. This is often quicker than guessing at absolute heading levels.
Dave
David Andrews | Chief Technology Officer
State Services for the Blind
2200 University Ave. W., Suite 240, St. Paul, MN 55114-1840
Direct: 651-539-2294 | Mobile: 612-730-7931
Web | Twitter | Facebook
-----Original Message-----
From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Birkir R. Gunnarsson
Sent: Friday, April 14, 2017 10:11 AM
To: WebAIM Discussion List < = EMAIL ADDRESS 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 ADDRESS 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 ADDRESS 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.
From: Lucy Greco
Date: Fri, Apr 14 2017 10:38AM
Subject: Re: JAWS 18 "no more headings at level X in this section"
← Previous message | Next message →
one quick corection the faster way to get to your serch is to hit q for
main and then 3 smile
Lucia Greco
Web Accessibility Evangelist
IST - Architecture, Platforms, and Integration
University of California, Berkeley
(510) 289-6008 skype: lucia1-greco
http://webaccess.berkeley.edu
Follow me on twitter @accessaces
On Fri, Apr 14, 2017 at 8:16 AM, Joseph Sherman < = EMAIL ADDRESS REMOVED = >
wrote:
> Great explanation, thanks.
>
> Joseph
>
>
> > -----Original Message-----
> > From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] On
> Behalf
> > Of Birkir R. Gunnarsson
> > Sent: Friday, April 14, 2017 11:11 AM
> > To: WebAIM Discussion List < = EMAIL ADDRESS 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 ADDRESS 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 ADDRESS 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.
> > > > > archives at
> > http://webaim.org/discussion/archives
> > > > > > >
From: J Isaac
Date: Fri, Apr 14 2017 1:42PM
Subject: Re: JAWS 18 "no more headings at level X in this section"
← Previous message | Next message →
I use this "H", "shit+H" approach as well for speed. It gives me the fastest way to understand the heading structure of the page outside of using the headings list.
-----Original Message-----
From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Andrews, David B (DEED)
Sent: Friday, April 14, 2017 9:37 AM
To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
Subject: Re: [WebAIM] JAWS 18 "no more headings at level X in this section"
I like the JAWS approach too, it gives you a little more idea of page organization by staying within a section. You can also use the h or shift-h commands to move to the next, or previous heading, whatever level it is at. This is often quicker than guessing at absolute heading levels.
Dave
David Andrews | Chief Technology Officer State Services for the Blind
2200 University Ave. W., Suite 240, St. Paul, MN 55114-1840
Direct: 651-539-2294 | Mobile: 612-730-7931 Web | Twitter | Facebook
-----Original Message-----
From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Birkir R. Gunnarsson
Sent: Friday, April 14, 2017 10:11 AM
To: WebAIM Discussion List < = EMAIL ADDRESS 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 ADDRESS 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 ADDRESS 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.
From: JP Jamous
Date: Fri, Apr 14 2017 2:36PM
Subject: Re: JAWS 18 "no more headings at level X in this section"
← Previous message | No next message
Joseph,
As Birkir stated, this is very useful rather than unuseful. When it tells you that there are no H3 on the page, it means that a higher level such as H1 or H2 proceed this H3.
This helps a visually impaired user to map out the nested headings in his or her mind like a sighted user sees it. I was frustrated at first with this change, but I know like it. In fact, it helps me tremendously if I am assessing a page.
-----Original Message-----
From: WebAIM-Forum [mailto: = EMAIL ADDRESS REMOVED = ] On Behalf Of Joseph Sherman
Sent: Friday, April 14, 2017 9:07 AM
To: WebAIM Discussion List < = EMAIL ADDRESS REMOVED = >
Subject: [WebAIM] JAWS 18 "no more headings at level X in this section"
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