Re: Should role=“contentinfo” be added on a footer or a p element?

Hi Yang,

I would also take into account how browsers map the footer element to
accessibility APIs.
In Firefox the footer is mapped to ARIA role=contentinfo
In Webkit/safari/chrome the footer is mapped to ARIA role=group if it is
contained within a section or article element otherwise it is mapped to
role=contentinfo
In IE it is not mapped

So doing this:
<div role=contentinfo>
some content
<footer> some content</footer>
</div>

will lead to nested contentinfo landmarks being announced in browsers that
already map footer to contentinfo.

I would suggest therefore that adding role=contentinfo to the main footer,
not worrying too much about content that you think may not be appropriate
being in the footer.

I would further suggest that use of role=group on footer elements contained
in section or article elements would be the way to go as it aligns the
semantics across browsers.


regards
stevef

On 26 June 2012 05:47, Ian Yang <ian.html@gmail.com> wrote:

> 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?
>
> <footer>
>     <nav>
>         <ul>
>             ........
>             ........
>             ........
>             ........
>             ........
>         </ul>
>     </nav>
>     <form>
>         ........
>         ........
>         ........
>     </form>
>     <p>© 2012 Website.com. All rights reserved.</p>
> </footer>
>
>
> Kind Regards,
> Ian Yang
>



-- 
with regards

Steve Faulkner
Technical Director - TPG

www.paciellogroup.com | www.HTML5accessibility.com |
www.twitter.com/stevefaulkner
HTML5: Techniques for providing useful text alternatives -
dev.w3.org/html5/alt-techniques/
Web Accessibility Toolbar - www.paciellogroup.com/resources/wat-ie-about.html