WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: Heading levels

for

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

> From: "Helen A" < <EMAIL REMOVED> >
>> 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 :-)

Further-

Let's go back to my original scenario and use your "explanation":

<h1>Creating Multi-Level CSS Menus</h1>
Intro

<h2>Adding the markup</h2>
Intro

<h3>Adding the Root-Level Markup</h3>
Steps

<h4>Adding the Sub-Level Markup</h3>
Steps

<h4>Creating the CSS</h2>
Intro

<h4>Creating Rules for Root-Level Menu Items</h3>
Steps

<h4>Creating Rules for Sub-Level Menu Items</h3>
Steps

Now that makes absolute no sense to me. Apparently, it makes little
sense to publishing software either, as that type of hierarchy would
not lend itself to any automated TOC generator. So again, what is the
logic behind this rule?

If an assistive reader user sets his program to list headings, then my
original scenario still makes a lot more sense than your answer does.
In fact, it makes perfect sense to a lot of people (which is why I
posed the original question). Please try to explain further, if you
will. I would love to teach this concept to our customers and to
employ it on our own site - if someone can provide the logic and not
just recite the specification :-)

Thanks.

--
Al Sparber
PVII
http://www.projectseven.com

"Designing with CSS is sometimes like barreling down a crumbling
mountain road at 90 miles per hour secure in the knowledge that
repairs are scheduled for next Tuesday".