This article discusses how to get rid of div elements altogether, and step into a world of pure semantics utilizing only lists for an entire page.

Now, why would we do this?

Because our content is really just a big list?

Because using can be confusing to user agents and so we need lists to present our ordered information?

Lets look at these individually.

Because our content is really just a big list

Now, from what the specs say about lists one could argue that the information contained in an html document is, if anything, “Ordered information”.

However, one look at example 1 from the article and its source code and it becomes obvious that this is just not semantically good.

A header and then it’s content on the next list item? In a nested unordered list no less? I feel like I’m heading back to tables!

Even if one could work out a sematically valid way of presenting this information (perhaps the header and it’s subsequent content held within the same

pair), do we need it?

Because using can be confusing to user agents and so we need lists to present our ordered information

Clearly something has been overlooked here, and part of what is missing can be found by reading Grouping elements: the DIV and SPAN elements from the W3C specs.

• RSS feed for comments on this post
• TrackBack URI