E-mail List Archives
Re: Providing accessible names with <title>
From: L Snider
Date: Sep 8, 2023 9:27AM
- Next message: Mike Warner: "mobile version of site and horizontal scroll arrows for content that extends off the screen"
- Previous message: L Snider: "Re: Providing accessible names with
"</a></li> <li><strong>Next message in Thread:</strong> None</li> <li><strong>Previous message in Thread:</strong> <a href="mail_message?id=49419">L Snider: "Re: Providing accessible names with <title>"</a></li> <li><a href="mail_thread?thread=10860">View all messages in this Thread</a></li> </ul> <hr> Oh and most of the people I work with don't access them, or it is far too<br /> much work to get to them.<br /> <br /> On Fri, Sep 8, 2023 at 12:26 PM L Snider < <EMAIL REMOVED> > wrote:<br /> <br /> > With the screen reader users (who rely on them, not test with them) I<br /> > know, they don't bother with the title. So in this case, I would use<br /> > ARIA...appropriate and not overriding any label or text that could be<br /> > provided and mirroring any link that is there for voice users. Others may<br /> > differ.<br /> ><br /> > Cheers<br /> ><br /> > Lisa<br /> ><br /> > On Thu, Sep 7, 2023 at 6:02 AM Nick Bromley < <EMAIL REMOVED> > wrote:<br /> ><br /> >> I'm testing a site that has a whole load of icon-based buttons that are<br /> >> named only with the <title> attribute. I know this isn't considered a good<br /> >> method of providing an accessible name, but it works across multiple<br /> >> browsers, devices, screen readers, and voice control software (although<br /> >> all<br /> >> reasonably modern, it has to be said). So when the W3C states in its<br /> >> <https://www.w3.org/WAI/ARIA/apg/practices/names-and-descriptions/><br /> >> 'Providing Accessible Names and Descriptions' authoring practice guidance<br /> >> that fallback mechanisms (of which <title> is one) "typically yield low<br /> >> quality accessible names that are not effective", is there anything I'm<br /> >> missing? Perhaps some more niche assistive technologies that I haven't<br /> >> verified it with? Or does it date back to a time when support was more<br /> >> patchy?<br /> >><br /> >> I'm minded to log a best practice recommendation to use aria-label<br /> >> instead,<br /> >> but could do with a bit more specific justification, if any exists.<br /> >><br /> >><br /> >><br /> >> - - -<br /> >><br /> >> Nick Bromley<br /> >><br /> >> Director & Accessibility Consultant<br /> >><br /> >> Red Kite Digital Accessibility Ltd<br /> >><br /> >> >> >> >> >><br /> > <hr> <ul> <li><strong>Next message:</strong> <a href="mail_message?id=49421">Mike Warner: "mobile version of site and horizontal scroll arrows for content that extends off the screen"</a></li> <li><strong>Previous message:</strong> <a href="mail_message?id=49419">L Snider: "Re: Providing accessible names with <title>"</a></li> <li><strong>Next message in Thread:</strong> None</li> <li><strong>Previous message in Thread:</strong> <a href="mail_message?id=49419">L Snider: "Re: Providing accessible names with <title>"</a></li> <li><a href="mail_thread?thread=10860&id=49420#49420">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">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/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>