Re: Proposal: <content> element

hi anne,
I agree, a problem i see with inferring things from the google stats is that
there is no indication of how often a class name is used on a page, also
what are the relative uses of these or similar values as id values?
if it is most often used singularly in the examples of
header/footer/content, this would indicate that allowing multiple instances
of these elements on a page, is not supported by the (unavailable) data.

2009/8/17 Anne van Kesteren <>

> Looking back at the Web Authoring Statistics
> I think the classes that indicated the need for an <article> in fact
> indicate the need for another element. Besides having a header and a footer
> most pages have some kind of element that indicates where the main content
> of the page is. I think that is what the classes "main" and "content"
> indicate. WAI-ARIA has a specific role for this purpose as well, "main".
> Presumably allowing AT to jump directly to the content of a page.
> If you consider a typical blog or news site you have a header, sidebar,
> footer, and a content area. The content area is not a single article, but
> usually (on the frontpage) consists of the latest ten articles or so. It
> seems perfectly logical to have some kind of grouping element for these just
> like many pages already do.
> I think that if you do the study again and also include the values of id
> attributes it will become even more clear, but simply studying templates of
> some blog engines probably does the trick too.
> --
> Anne van Kesteren

with regards

Steve Faulkner
Technical Director - TPG Europe
Director - Web Accessibility Tools Consortium |
Web Accessibility Toolbar -

Received on Monday, 17 August 2009 09:59:08 UTC