E-mail List Archives

You are here: Home > Community > E-mail List Archives > View Message

Re: ARIA landmarks, why are they not more descriptive?

From: Dylan Barrell
Date: Jan 28, 2013 2:38PM

Next message: Keith Parks: "Re: content order?"</a></li> <li><strong>Previous message:</strong> <a href="mail_message?id=22102">Paul J. Adam: "Re: <title> content order?"</a></li> <li><strong>Next message in Thread:</strong> <a href="mail_message?id=22112">Henny Swan: "Re: ARIA landmarks, why are they not more descriptive?"</a></li> <li><strong>Previous message in Thread:</strong> <a href="mail_message?id=22098">Rakesh: "Re: ARIA landmarks, why are they not more descriptive?"</a></li> <li><a href="mail_thread?thread=5693">View all messages in this Thread</a></li> </ul> <hr> Birkir,<br /> <br /> Here is the way that I recommend use of landmarks:<br /> <br /> 1) role="main" for the main content of the page and the container for the<br /> target of the skip to main content link (1 per page)<br /> 2) role="search" for the container of the search form (generally 1 per page<br /> but could be more)<br /> 3) role="banner" for the header of the page (1 per page)<br /> 4) role="contentinfo" for the footer of the page or the portion of the page<br /> that includes legal and copyright information (0 or 1 per page)<br /> 5) role="navigation" for any navigational container (generally more than 1<br /> per page)<br /> <br /> Other landmark roles are less common, you could use role="form" on all<br /> forms but this is somewhat redundant in most ATs and role="complementary"<br /> is always going to be somewhat open to interpretation.<br /> <br /> --Dylan <hr> <ul> <li><strong>Next message:</strong> <a href="mail_message?id=22104">Keith Parks: "Re: <title> content order?"</a></li> <li><strong>Previous message:</strong> <a href="mail_message?id=22102">Paul J. Adam: "Re: <title> content order?"</a></li> <li><strong>Next message in Thread:</strong> <a href="mail_message?id=22112">Henny Swan: "Re: ARIA landmarks, why are they not more descriptive?"</a></li> <li><strong>Previous message in Thread:</strong> <a href="mail_message?id=22098">Rakesh: "Re: ARIA landmarks, why are they not more descriptive?"</a></li> <li><a href="mail_thread?thread=5693&id=22103#22103">View all messages in this Thread</a></li> </ul> </div> </article>  <aside id="articlemeta"> </aside> </main> <footer> <div id="footerresources"> <div class="footerblock"> <h2 id="copyright">©2024 WebAIM</h2> <p id="contact"><a href="https://idrpp.usu.edu/">Institute for Disability Research, Policy, and Practice</a><br> Utah State University<br> 6807 Old Main Hill<br> Logan, UT 84322-6807<br> <a class="phone" href="tel:4357977024">435.797.7024</a></p> <div id="checkpage"> <h2>Check Your Accessibility</h2> <form action="https://wave.webaim.org/report" novalidate> <label for="waveurl">Web site address:</label> <input type="url" id="waveurl" name="url" title="Web site address"> <input type="submit" value="WAVE"> </form> </div> </div> <div class="footerblock"> <h2 id="blog">From the Blog</h2> <ul><li><a href="/blog/severity-ratings/">Using Severity Ratings to Prioritize Web Accessibility Remediation</a></li><li><a href="/blog/25-tips/">25 Accessibility Tips to Celebrate 25 Years</a></li><li><a href="/blog/celebrating-webaims-25th-anniversary/">Celebrating WebAIM's 25th Anniversary</a></li><li><a href="/blog/introducing-ncademi/">Introducing NCADEMI: The National Center on Accessible Digital Educational Materials & Instruction </a></li></ul> </div> <div class="footerblock"> <h2 id="popular">Popular Resources</h2> <ul> <li><a href="/training/virtual">WebAIM Training</a></li> <li><a href="/standards/wcag/checklist">WCAG 2 Checklist</a></li> <li><a href="/newsletter">WebAIM Monthly Newsletter</a></li> <li><a href="/resources/contrastchecker">Color Contrast Checker</a></li> <li><a href="/resources/designers/">Web Accessibility for Designers</a></li> <li><a href="http://wave.webaim.org/">WAVE Web Accessibility Evaluation Tool</a></li> </ul> </div> <div id="footerlinks"> <ul> <li><a id="footercontact" href="/contact">Contact</a></li> <li><a id="footerabout" href="/about">About</a></li> <li><a id="footerrss" href="/community/rss">RSS Feeds</a></li> <li><a id="footertwit" href="http://twitter.com/webaim">Twitter</a></li> <li><a id="footercopyright" href="/copyright">Copyright & Terms of Use</a></li> </ul> </div> <div class="clear"></div> </div> </footer> </body> </html>