E-mail List Archives
Re: <title> content order?
From: Paul J. Adam
Date: Jan 28, 2013 11:35AM
- Next message: Dylan Barrell: "Re: ARIA landmarks, why are they not more descriptive?"
- Previous message: Angela French: "Re:
content order?"</a></li> <li><strong>Next message in Thread:</strong> <a href="mail_message?id=22104">Keith Parks: "Re: <title> content order?"</a></li> <li><strong>Previous message in Thread:</strong> <a href="mail_message?id=22101">Angela French: "Re: <title> content order?"</a></li> <li><a href="mail_thread?thread=5703">View all messages in this Thread</a></li> </ul> <hr> Hi Rick, good question! I see many sites that first put their site name at the beginning of every single page title forcing you to have to look at the end of the page title to see the name of the page your located on. A screen reader user would have to listen to the page title as the very first item on the page and would have to hear the site name every single time to determine the actual page name. Also when you have many tabs opened in a browser you only see the first few words of that tab so if the page name is at the very end of the title it would be cut off from view in the tab. <br /> <br /> For those reasons I recommend you start with the most important info and that is the actual page title, not the site name. Users already know the site name based on the URL as well. <br /> <br /> Best practice would be, as an example of a contact page for the english department of a university, <title>Contact Us - English Dept. - State University System</title>. <br /> <br /> Paul J. Adam<br /> Accessibility Evangelist <br /> Deque Systems<br /> <EMAIL REMOVED> <br /> <a href="http://www.PaulJAdam.com">www.PaulJAdam.com</a><br /> @pauljadam on Twitter<br /> <br /> On Jan 28, 2013, at 12:17 PM, Rick Hill < <EMAIL REMOVED> > wrote:<br /> <br /> > In <title> which is order is preferred (and why) or is either OK:<br /> > <br /> > <title>Page info : Site Name</title><br /> > <br /> > or<br /> > <br /> > <title>Site Name: Page Info</title><br /> > <br /> > Examples:<br /> > <br /> > <title>Test Page : UC Davis</title><br /> > <br /> > or<br /> > <br /> > <title>UC Davis : Test Page</title><br /> > -------------------------------------------------------------------<br /> > Rick Hill, Web CMS Administrator<br /> > University Communications, UC Davis<br /> > (530) 752-9612<br /> > <a href="http://cms.ucdavis.edu">http://cms.ucdavis.edu</a><br /> > -------------------------------------------------------------------<br /> > Web CMS assistance at <EMAIL REMOVED> <mailto: <EMAIL REMOVED> ><br /> > -------------------------------------------------------------------<br /> > <br /> > > > <hr> <ul> <li><strong>Next message:</strong> <a href="mail_message?id=22103">Dylan Barrell: "Re: ARIA landmarks, why are they not more descriptive?"</a></li> <li><strong>Previous message:</strong> <a href="mail_message?id=22101">Angela French: "Re: <title> content order?"</a></li> <li><strong>Next message in Thread:</strong> <a href="mail_message?id=22104">Keith Parks: "Re: <title> content order?"</a></li> <li><strong>Previous message in Thread:</strong> <a href="mail_message?id=22101">Angela French: "Re: <title> content order?"</a></li> <li><a href="mail_thread?thread=5703&id=22102#22102">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">©2021 WebAIM</h2> <p id="contact">Institute for Disability Research, Policy, and Practice<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/seismic-change-to-docs/">Google Announces Seismic Change to Docs</a></li><li><a href="/blog/colorado-mandates-accessibility/">Colorado Mandates Accessibility for State and Local Government Websites</a></li><li><a href="/blog/contrast-how-hard-can-it-be/">Evaluating Color and Contrast - How hard can it be?</a></li><li><a href="/blog/show-up-to-disrupt/">Show Up to Disrupt</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>