RE: Having h5 after h2 is a violation as per 1.3.1 info & relationships. - was: WCAG violations or accessibility enhancements

While i agree that skipping levels is not a WCAG violation,  it should be
emphasised that this will cause a usability problem for screenreader users.
 E.g. if a screenreader user cycles through the headings (h1, h2's then
h3's, etc. ) and the screenreader reported nothing for a next level of
heading (i.e.,  h3 and h4 skipped), then the user will most likely stop
cycling through headings,  having assumed there were no further headings.
In this case the screenreader user will not be presented with an
*equivalent* 'picture' of the page as we,  the sighted user will perceive
it.
If it's not an explicit rule of WCAG, then it's high time we made it a
rule!

Kindest regards
Harry


On 3 Mar 2018 03:42, "Jonathan Avila" <jon.avila@levelaccess.com> wrote:

> > We could call it an "outline algorithm" perhaps. And then wait for
> browsers to actually implement it in a meaningful way too?
>
> Yes, too bad this wasn't sent on February 2nd -- perhaps the second time
> around is a charm and we'll also be better piano players.
>
> Jonathan
>
> -----Original Message-----
> From: Patrick H. Lauke [mailto:redux@splintered.co.uk]
> Sent: Friday, March 2, 2018 9:59 AM
> To: w3c-wai-ig@w3.org
> Subject: Re: Having h5 after h2 is a violation as per 1.3.1 info &
> relationships. - was: WCAG violations or accessibility enhancements
>
> On 02/03/2018 14:51, Glenda Sims wrote:
> > Crazy idea o' the week.  This problem of heading structure never
> > happens to us in ordered lists..because we let the browsers render the
> > list numbers.  Wouldn't it be super cool if we could have a similar
> > construct in html for headings.
> >
> > I've only had one cup o' coffee....so this may not be the best idea I
> > ever had...
> >
> > Example of dynamic heading structure
> > <oh>  Glenda's make believe ordered headings
> >     <hi>  Glenda's make believe heading item </hi>
> >     <oh>
> >          <hi> Another make believe heading item </hi> <!--#include
> > file="includewithheading.html" -->
> >          <hi>The last heading in this example</hi>
> > <!-- end of include -->
> >      </oh>
> > </oh>
>
> We could call it an "outline algorithm" perhaps. And then wait for
> browsers to actually implement it in a meaningful way too?
>
> P
> --
> Patrick H. Lauke
>
> www.splintered.co.uk | https://github.com/patrickhlauke
> http://flickr.com/photos/redux/ | http://redux.deviantart.com
> twitter: @patrick_h_lauke | skype: patrick_h_lauke
>
>