WebAIM - Web Accessibility In Mind

E-mail List Archives

RE: Heading levels

for

From: Andrew Arch
Date: Jun 25, 2006 10:50PM


Nothing wrong with your semantics - blame the tool :)

Basically, the rule that we apply is don't skip levels on the way down, you
can jump back up to any level (though most would argue that a page should
only have one H2).

Think about it like a text book table of contents - does it make sense then?
Are all the sub-sub-headings subservient to the right sub-headings? Etc. The
AIS Web Accessibility Toolbar [1] has a nice headings call out feature to
give you the relative levels of all headings on a page (in a new window to
separate them from the content for analytical purposes) - see
structure/heading-structure.

Andrew

[1] www.visionaustralia.org.au/ais/toolbar/

-----Original Message-----
From: <EMAIL REMOVED>
[mailto: <EMAIL REMOVED> ]On Behalf Of Al Sparber
Sent: Monday, 26 June 2006 2:44 AM
To: Webaim
Subject: [WebAIM] Heading levels


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

It seems perfectly logical to me, but apparently this is not correct?

--

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".









___________________
<< ella for Spam Control >> has removed Spam messages and set aside Later
for me
You can use it too - and it's FREE! http://www.ellaforspam.com