W3C home > Mailing lists > Public > w3c-wai-ig@w3.org > October to December 2009

Re: More than one h1 tag

From: Harry Loots <harry.loots@ieee.org>
Date: Wed, 2 Dec 2009 10:16:43 +0100
To: w3c-wai-ig@w3.org
Message-Id: <20091202091643.M3702@ieee.org>
Ironically, Michael, the point perhaps more clearly illustrates why there
should be 1 H1 per page. A website is made up of a collection of webpages in
the same way as a book is made up of chapters. The webpage is the chapter - it
takes on the parent title (H1), and every other title (H2-H6) on this page
(chapter) should relate directly to the parent title (H1), otherwise it should
be better to split the page into multiple pages. 

Kind regards
Harry

~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~.~


---------- Original Message -----------
From: Michael Virant <mwvirant@gmail.com>
To: w3c-wai-ig@w3.org
Sent: Wed, 2 Dec 2009 13:15:04 +1100
Subject: Re: More than one h1 tag

> My view is that the web page TITLE is being conflated with the web page's
> one or more H1 tags in this topic.  Just as a book has one title it
> typically has several chapters.  Hence a web page should have one 
> title and as many H1 tags as is necessary to convey the same 
> structure.  Then within in chapter (section with heading H1) there 
> may or may not be the need to order future sub headings (H2) all 
> related to the H1 above it.
> 
> The alternative - to have only one H1 followed by one or more H2, H3 
> is disorientating for all users as it is an artificial 
> representation of the data.  For example if the second section 
> (under a H2) of a document bears no relation to the first section 
> (with H1) then semantic markup forces the relationship of the second 
> section to be a child of the first section when there is no such elationship.
> 
> Michael Virant
------- End of Original Message -------
Received on Wednesday, 2 December 2009 09:17:33 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 19 July 2011 18:14:33 GMT