E-mail List Archives

RE: Heading levels

for

From: Jon Gunderson
Date: Jun 26, 2006 9:00AM


The functional accessibility evaluator [1] allows any heading
level before the last H1 element (Note: H1 are reserved for
titling pages and the last H1 is considered the sub page title
of a page [2]). After the last H1 the heading should use
hierarchical structure. H2 should also be used to label
navigation bars[3], so there maybe h2 before the first H1 element.

Jon

[1] Functional Accessibility Evaluator
http://fae.cita.uiuc.edu

[2] HTML Best practices: Unique titles
http://html.cita.uiuc.edu/nav/title.php

[3] HTML Best practices: Navigation bars and menus
http://html.cita.uiuc.edu/nav/menus.php


---- Original message ----
>Date: Mon, 26 Jun 2006 15:28:10 +1000
>From: "Andrew Arch" < <EMAIL REMOVED> >
>Subject: RE: [WebAIM] Heading levels
>To: "'WebAIM Discussion List'" < <EMAIL REMOVED> >
>
>Oops - typo - I meant to say that many folk would suggest
there should only
>be one H1. There can be many H2s.
>
>Sorry, Andrew
>
>-----Original Message-----
>From: <EMAIL REMOVED>
>[mailto: <EMAIL REMOVED> ]On Behalf Of
Andrew Arch
>Sent: Monday, 26 June 2006 2:43 PM
>To: 'WebAIM Discussion List'
>Subject: RE: [WebAIM] Heading levels
>
>
>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
>
>
>
>
>
>
>___________________
><< 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
>
>
>
>


Jon Gunderson, Ph.D.
Director of IT Accessibility Services
Campus Information Technologies and Educational Services (CITES)
and
Coordinator of Assistive Communication and Information Technology
Disability Resources and Education Services (DRES)

Voice: (217) 244-5870
Fax: (217) 333-0248
Cell: (217) 714-6313

E-mail: <EMAIL REMOVED>

WWW: http://cita.rehab.uiuc.edu/
WWW: https://netfiles.uiuc.edu/jongund/www/