WebAIM - Web Accessibility In Mind

E-mail List Archives

Re: landmarks in landmarks

for

From: Jacek Zadrożny
Date: Dec 12, 2013 2:05AM

Thanks so much. But I have more questions. I read an article and I think
it's tru. But what about mixing HTML structural elements and landmarks?
OK. So if there is an footer element of HTML5 it means that using ARIA
role "content-info" is wrong? For me landmarks are for blind users to
quickly navigate to navigation, main content or footer. Most of
screenreaders have no navigation mechanism using HTML5 structural
elements, but using landmarks. So what is good solution? Is it invalid:
<footer aria-role="content-info">?
Jacek

W dniu 2013-12-11 17:32, Jared Smith pisze:
> It is OK to embed landmark roles within other landmark roles. However,
> I think it is assumed that the contentinfo landmark will contain links
> about the site, copyright, etc. While the ARIA specification does not
> state this, the HTML5 spec does clarify that <footer> (which maps to
> the contentinfo role - see
> http://www.brucelawson.co.uk/2013/why-does-html-take-rolecontentinfo/)
> should not include <nav> (which maps to the navigation role) for such
> links.
>
> I also don't think of such links as "navigation" in the strictest
> sense. I would probably drop the navigation landmark from within the
> contentinfo landmark/footer.
>
> Jared
> > > --
Jacek Zadrożny
http://informaton.pl
[AAA} All About Accessibility