E-mail List Archives
Re: Providing accessible names with <title>
From: Nick Bromley
Date: Sep 7, 2023 3:35AM
- Next message: Nick Bromley: "Re: Providing accessible names with
" - Previous message: Birkir R. Gunnarsson: "Re: Providing accessible names with
" - Next message in Thread: Nick Bromley: "Re: Providing accessible names with
" - Previous message in Thread: Birkir R. Gunnarsson: "Re: Providing accessible names with
" - View all messages in this Thread
I think the vast majority of the user group of this particular site are likely to be using non-ancient tech, but I think I'll still log a recommendation to update the naming approach while still retaining the <title> attribute as it does provide some benefit for certain users. Good point about use of hidden text.
-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Steve Green
Sent: Thursday, September 7, 2023 10:20 AM
To: WebAIM Discussion List < <EMAIL REMOVED> >
Subject: Re: [WebAIM] Providing accessible names with <title>
The "title" attribute has been part of the Accessible Name Computation for a long time, so all user agents should use it if an accessible name is not provided by a higher priority method. It's certainly sufficient for WCAG conformance, even if it's a bit nasty.
I don't know of any assistive technologies that don't use the "title" attribute if necessary. There might be some, but now we're returning to the age old question of whether we need to worry about user agents that don't support current standards.
I just had the same issue on a website and recommended that the accessible name should be implemented as hidden text if possible (because non-ARIA solutions should be the first choice), otherwise by an "aria-label" attribute.
Steve Green
Managing Director
Test Partners Ltd
-----Original Message-----
From: WebAIM-Forum < <EMAIL REMOVED> > On Behalf Of Nick Bromley
Sent: Thursday, September 7, 2023 10:02 AM
To: 'WebAIM Discussion List' < <EMAIL REMOVED> >
Subject: [WebAIM] Providing accessible names with <title>
I'm testing a site that has a whole load of icon-based buttons that are named only with the <title> attribute. I know this isn't considered a good method of providing an accessible name, but it works across multiple browsers, devices, screen readers, and voice control software (although all reasonably modern, it has to be said). So when the W3C states in its <https://www.w3.org/WAI/ARIA/apg/practices/names-and-descriptions/>
'Providing Accessible Names and Descriptions' authoring practice guidance that fallback mechanisms (of which <title> is one) "typically yield low quality accessible names that are not effective", is there anything I'm missing? Perhaps some more niche assistive technologies that I haven't verified it with? Or does it date back to a time when support was more patchy?
I'm minded to log a best practice recommendation to use aria-label instead, but could do with a bit more specific justification, if any exists.
- - -
Nick Bromley
Director & Accessibility Consultant
Red Kite Digital Accessibility Ltd
- Next message: Nick Bromley: "Re: Providing accessible names with
" - Previous message: Birkir R. Gunnarsson: "Re: Providing accessible names with
" - Next message in Thread: Nick Bromley: "Re: Providing accessible names with
" - Previous message in Thread: Birkir R. Gunnarsson: "Re: Providing accessible names with
" - View all messages in this Thread