- From: Jeremy Keith <jeremy@adactio.com>
- Date: Sat, 29 Aug 2009 13:43:16 +0100
- To: Lachlan Hunt <lachlan.hunt@lachy.id.au>
- Cc: Henri Sivonen <hsivonen@iki.fi>, HTML WG <public-html@w3.org>, W3C WAI-XTECH <wai-xtech@w3.org>
Lachy wrote: > I'm not so keen on using the name <main>, and would prefer we used > <content>. <main> seems like it could only be used once per > document, but if we introduce an element for this purpose, it should > be able to be used within multiple sections of a page, just like > header and footer can be. But Lachlan, the spec has already gone down the road of repurposing global-sounding names with <header> and <footer>. The overwhelming usage of the words "header" and "footer" in class names is once per document. Most web developers that I've spoken to expressed surprise that the <header> and <footer> elements in HTML5 could be used more than once. That's because the terms "header" and "footer" *sound like* content that appears once per document. Note that I'm not saying that having multiple <header>s and <footer>s in a document is wrong, I'm just saying that it is counter-intuitive to most web developers and doesn't match the majority usage of those words. So if you have an objection to naming an element <main> because it *sounds like* it can only be used once per document, that same objection would have to apply to <header> and <footer> — they *sound like* like they can only be used once per document. In short, I think the word "main" is as good as "header" and "footer" and I'd be favour of naming a new element <main> to match the aria role="main". But you do raise a good point about the names of elements not matching what most people use the corresponding words to mean. In my opinion, the content model of <footer> (which is far more restrictive than <header) is *extremely* counter-intuitive and is going to cause a lot of confusion amongst web developers using the <footer> element for the content at the bottom of their pages that they commonly refer to (and have referred to for years) as "the footer". Either: 1) The name of the element <footer> needs to changed to something more suitable (like <contentinfo> which would match the ARIA role) or 2) The content model of <footer> needs to be expanded to match that of <header>. -- Jeremy Keith a d a c t i o http://adactio.com/
Received on Saturday, 29 August 2009 12:44:00 UTC