E-mail List Archives
Re: Header tag
From: Simon Jessey
Date: Apr 30, 2003 6:17PM
- Next message: Lori K. Brown: "Re: Header tag"
- Previous message: Lori K. Brown: "Re: Header tag"
- Next message in Thread: Lori K. Brown: "Re: Header tag"
- Previous message in Thread: Simon Jessey: "Re: Header tag"
- View all messages in this Thread
----- Original Message -----
From: "Lori K. Brown" < <EMAIL REMOVED> >
Subject: Re: Header tag
> My assumption, reading J. Foliot's lucid example, is that there is STUFF,
> that is to say, paragraphs and things, following each of the headings. So,
> no, Simon, it's not a list.
I think perhaps you misunderstand what I meant by a list. To see an example
of how list markup can be used, see my weblog (in my signature). Each entry
is a list item, and each item can have headings, paragraphs, tables, images
and other elements. Using list markup creates a logical, hierachical
structure (with semantic richness) for something that has many sections and
subsections. Such an approach is widely used by forward-thinking web
designers because of its good structure, accessibility and easy-to-style
If you think about it, a collection of 'sections', which in turn may have
collections of sub-sections, are nothing more than nested ordered or
unordered lists. Since list markup can contain pretty much anything, it
makes sense to use it.
In cases where such an approach cannot work, my _recommendation_ is to try
and break things up into shorter documents, to _avoid_ messing with the
structured nature of headings. I have created countless pages and I have
thus far not found the need to break that heading structure in the way this
thread has described.
<< Simon, you are bending over backwards to defend an illogical and
indefensible interpretation of the standards. Separate pages for each? That
is simply bananas. If they were trying to make me roll my eyes and give up
on validation, this goes a long way toward success. Any architecture that
requires us to break things up into arbitrary tiny pieces is just crazy
It is unfortunate that you have chosen to interpret my suggestions in this
way. I assure you, my intention was merely to contribute to an interesting
discussion, and to give my thoughts on the perceived fault in the Bobby
tool. I am a regular user of Bobby because I like to do my best to ensure my
web pages are as accessible as possible. I consider Bobby 'approval' to be
as necessary as HTML validation, so it is important to me that the client
e: <EMAIL REMOVED>
To subscribe, unsubscribe, or view list archives,