WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Heading levels

for

From: Al Sparber
Date: Jun 25, 2006 11:10AM

From: "Helen A" < <EMAIL REMOVED> >
To: "WebAIM Discussion List" < <EMAIL REMOVED> >
Sent: Sunday, June 25, 2006 12:55 PM
Subject: Re: [WebAIM] Heading levels


> At 17:43 25/06/2006, Al Sparber wrote:
>>Can someone provide a plain language explanation of why
>>non-sequential headings might be considered inaccessible? For
>>example, the following scenario fails in an online automated
>>checker.
>><h1>Creating Multi-Level CSS Menus</h1>
>>Intro
>><h2>Adding the markup</h2>
>>Intro
>><h3>Adding the Root-Level Markup</h3>
>>Steps
>><h3>Adding the Sub-Level Markup</h3>
>>Steps
>><h2>Creating the CSS</h2>
>>Intro
>><h3>Creating Rules for Root-Level Menu Items</h3>
>>Steps
>><h3>Creating Rules for Sub-Level Menu Items</h3>
>>Steps
>
> its because you have gone from <h3> back to <h2>. You can't
> back-track up a level, so working down a page you can't have <h3> on
> line N then on line Q put <h2>, it would have to be <h4> as 4
> follows 3 numerically speaking.

I understand the rule, my question concerns the logic. It doesn't make
sense. Is this, then, one of those areas where one follows the rule to
pass a test, throwing logic to the wind?

In my scenario, I would most certainly want to go back. Perhaps that's
why a lot of online tutorials are hard for me to follow :-)

--
Al