Is it time to stop vilifying the Title attribute
on a form field
I tweeted the following:
<button aria-label="Facebook" title="Facebook"><span class="icon-font-fb" aria-hidden="true"></span></button> ... ACCNAME is aria-label ACCDESCRIPTION is title. screen reader speaks twice, title on hover is good but not keyboard. Wish for elegant native HTML solution.
— David MacDonald (@davidmacd) April 22, 2019
It generated a fairly interesting conversation among some colleagues who work on standards
Removing aria-label would fix the double-reading here wouldn't it?
— James Nurthen (@jnurthen) April 22, 2019
The vilification of the use of title as an accessible name has caused a lot of these issues. Sometimes it is the right thing to use (not often mind you). Adding the same text as title in aria-label is rarely the right resolution.
— James Nurthen (@jnurthen) April 22, 2019
Feel free to comment on Twitter @davidmacdI'm inclined to say drop aria-label from it also... AXE passes it, but WAVE fails it and many lawsuits these days are quoting Wave. So dropping aria-label could cause legal noise and leaving it causes screen reader noise. :(@jared_w_smith
— David MacDonald (@davidmacd) April 23, 2019
Author information:
David MacDonald is a veteran WCAG member, co-editor of Using WAI ARIA in HTML5 and HTML5 Accessibility Task Force Member. Opinions are my own.
CONTACT US
For a quote or just to chat about your organization's needs
