E-mail List Archives
Providing accessible names with <title>
From: Nick Bromley
Date: Sep 7, 2023 3:01AM
- Next message: Steve Green: "Re: Providing accessible names with
" - Previous message: Nick Bromley: "Re: PowerPoint Issue"
- Next message in Thread: Steve Green: "Re: Providing accessible names with
" - Previous message in Thread: None
- View all messages in this Thread
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: Steve Green: "Re: Providing accessible names with
" - Previous message: Nick Bromley: "Re: PowerPoint Issue"
- Next message in Thread: Steve Green: "Re: Providing accessible names with
" - Previous message in Thread: None
- View all messages in this Thread