E-mail List Archives
Re: Providing accessible names with <title>
From: Jeremy Echols
Date: Sep 7, 2023 7:20AM
- Next message: Yeti: "Re: Providing accessible names with
" - Previous message: Nick Bromley: "Re: Providing accessible names with
" - Next message in Thread: Yeti: "Re: Providing accessible names with
" - Previous message in Thread: Nick Bromley: "Re: Providing accessible names with
" - View all messages in this Thread
One thing I've run across recently with NVDA and Firefox is when people use title too much, they start putting it on things that already have text just because they get in the habit of adding a title to every last thing. With Firefox and NVDA, a link with a title will double up the announcement. For instance, this markup results in "Next - Setup and Installation link Setup and Installation":
<a href="somewhere" title="Setup and Installation">Next - Setup and Installation</a>
This is still probably not a WCAG conformance issue, but it can be confusing, and is just one more reason to try to push people away from using it. Note that I hear similar issues when there's both a title and another accessible name, such as "aria-label".
I'm not sure why NVDA and/or Firefox are using both values instead of ignoring the title here, but it's definitely sub-par. And once devs get in the habit of using it, they seem to just love to put it on everything. The example above is from a documentation project I'm working on, and it's got titles in some of the weirdest places.
- Next message: Yeti: "Re: Providing accessible names with
" - Previous message: Nick Bromley: "Re: Providing accessible names with
" - Next message in Thread: Yeti: "Re: Providing accessible names with
" - Previous message in Thread: Nick Bromley: "Re: Providing accessible names with
" - View all messages in this Thread