W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > January to March 2005

Re: [techs] Review of tests 37, 38, 39, 40, 41 - Header nesting

From: Roberto Scano - IWA/HWG <rscano@iwa-italy.org>
Date: Wed, 23 Feb 2005 22:17:00 +0100
Message-ID: <01d501c519ed$05c6def0$0200a8c0@iwars>
To: "Chris Ridpath" <chris.ridpath@utoronto.ca>, "Joe Clark" <joeclark@joeclark.org>, "WAI-GL" <w3c-wai-gl@w3.org>


----- Original Message ----- 
From: "Chris Ridpath" <chris.ridpath@utoronto.ca>
To: "Joe Clark" <joeclark@joeclark.org>; "WAI-GL" <w3c-wai-gl@w3.org>
Sent: Wednesday, February 23, 2005 10:03 PM
Subject: Re: [techs] Review of tests 37, 38, 39, 40, 41 - Header nesting



37 The header following an h1 is h1 or h2.
http://www.w3.org/WAI/GL/WCAG20/tests/test37.html

Roberto Scano:
This is right if we consider the <title> Element like an "<h0>". 
Otherwise (referring for eg. to an e-book structure), <h1> is the most 
important title in the page (so, for eg., a chapter title) so in the 
same page shouldn't be more than one <h1>.



Chris Ridpath:
Meyer's article that gives a good argument for allowing skipping levels:
http://www.meyerweb.com/eric/thoughts/2004/07/21/pick-a-heading/

What's your take?

Roberto Scano:
I disagree with Eric. Please look at outline of his web site:
http://validator.w3.org/check?uri=http://www.meyerweb.com/;outline=1

Below is an outline for this document, automatically generated from the 
heading tags (<h1> through <h6>.)

meyerweb .com
  A level 2 heading is missing!
    A level 3 heading is missing!
      Exploration
    Taking The "A" Train
    Upcoming Events
    Very Sneaky
    Airport Extreme and Netgear MR814v2, Take 2
    I Miss PhotoBars
    New Design, New Feeds
    Breakfast Bliss
    S5 1.1b5
      Destinations
      Distractions
      Redesign Watch
        Blog Watch
      The excuse of the day is
      Extras
      Navigation

Document isn't correctly formatted.
Did u understand contents referring to these headings?
If for eg. I take this page "as is" and try to create an accessible PDF, 
I receive the same errors from the Accessibility Checker. Without 
respecting the headings structure (in HTML but also in other languages 
that follow this method for structure documents) users can have 
difficulty to see important contents and reach what they desire.

Try instead:
http://validator.w3.org/check?uri=http://www.w3.org/;outline=1
http://validator.w3.org/check?uri=http://www.w3.org/wai;outline=1

This is what we need to require (btw, we require it in the italian law, 
as first requirement)
Received on Wednesday, 23 February 2005 21:17:12 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:47:35 GMT