- From: Bruce Lawson <bruce@brucelawson.co.uk>
- Date: Tue, 26 Jun 2012 10:12:35 +0100
- To: w3c-wai-ig@w3.org
>> Hi everyone,
>>
>> On ARIA demonstration websites, role="contentinfo" is usually added on a
>> footer element.
>>
>> However, footers in modern web
>> design<http://www.smashingmagazine.com/2008/04/08/footers-in-modern-web-design-creative-examples-and-ideas/>can
>> be creative so that they can also contain things like supplementary
>> navigation links, social website links, or even a newsletter form.
>>
>> Taking the following codes of footer for example. Should
>> role="contentinfo" be added on the footer or the p element?
In such a case, I'd probably put the role of contentinfo on div (or a p)
if there is lots of supplementary blah in the footer. But "supplementary
navigation links, social website links, or even a newsletter form" might
legitimately be role=contentinfo, too (which ARIA spec says "A large
perceivable region that contains information about the parent document ..
Examples of information included in this region of the page are copyrights
and links to privacy statements.)
It depends on the content.
The biggest difference to be aware of between html5 <footer> and ARIA
contentinfo is that there can be any number of <footer>s on a page, but
only one role="contentinfo". ("Within any document or application, the
author SHOULD mark no more than one element with the contentinfo role.")
The same is true of <header> and role=banner. Also, <address> may be given
an ARIA role of contentinfo, too.
http://dev.w3.org/html5/spec/wai-aria.html#table-aria-weak
bruce
(Author "Introducing HTML5" http://www.introducinghtml5.com)
Received on Tuesday, 26 June 2012 09:13:14 UTC