Hi Julián,
SEMANTICS EXTRACTOR
Sometimes a view that approximates the semantics
of the content can be useful. Fortunately the W3C
have just such a tool: <
http://www.w3.org/2003/12/semantic-extractor.html >.
This will likely affirm Paul's point regarding an
<h3> as a 'parent' to an <h2> element (i.e.
don't).
INDEX vs CONTENT PAGES
It's also worth distinguishing between index and
content pages when considering use of heading
elements to impose structure. (An index page
being an entry-point to a section of a website,
for example a list of recent articles structured
by topic.) For this type of page you might want
to re-jig the hierarchies, e.g.:
<h1>Articles</h1>
<h2>Topic</h2>
<h3>Article title</h3>
<h3>Article title</h3>
<h3>Article title</h3>
<h2>Topic</h2>
<h3>Article title</h3>
<h3>Article title</h3>
<h3>Article title</h3>
If you have articles and guide on the same page,
then this would be one of the rare instances
where multiple <h1> elements may be appropriate.
<h1> AND WEBSITE NAME/TITLE
I wouldn't recommend using an <h1> for the
website title. If you're concerned with
identifying the website (for example to screen
readers) then include the website name/title in
the <title> element, e.g:
<head>
<title>Content title | Website name</title>
</head>
<body>
<h1>Content title</h1>
...
</body>
See 'Typical user scenario: 1-7 for an outline of
how a screen reader may interpret page elements':
<
http://www.standards-schmandards.com/index.php?2005/01/10/13-browsing-habits >
For more on the title element < http://www.motive.co.nz/glossary/meta.php >
Best regards,
--
Andy Kirkwood | Creative Director
Motive | web.design.integrity
http://www.motive.co.nz
ph: (04) 3 800 800 fx: (04) 970 9693
mob: 021 369 693
93 Rintoul St, Newtown
PO Box 7150, Wellington South, New Zealand
******************************************************
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
******************************************************
