E-mail List Archives
Re: Providing accessible names with <title>
From: Mark Magennis
Date: Sep 7, 2023 9:58AM
- Next message: Yeti: "Re: Form fields in a sentence"
- Previous message: Mark Magennis: "Form fields in a sentence"
- Next message in Thread: Nick Bromley: "Re: Providing accessible names with
" - Previous message in Thread: Yeti: "Re: Providing accessible names with
" - View all messages in this Thread
Nick, when you say the <title> attribute provides some benefit for certain users, do you mean that browsers sometimes generate tooltips containing it? If so, I wouldn't refer to this as a benefit because if a button needs a tooltip, and in my opinion all icon-only buttons do need tooltips, then the browser-generated tooltip will only be displayed by some browsers and support is dwindling. It used to be only Firefox that didn't display a tooltip with the <title> but now I believe it's Chrome and Edge as well. So this isn't a reliable method of providing a benefit and if it is needed it can't really be called a benefit.
From: WebAIM-Forum < <EMAIL REMOVED> > on behalf of Nick Bromley < <EMAIL REMOVED> >
Sent: Thursday 7 September 2023 10:35
To: 'WebAIM Discussion List' < <EMAIL REMOVED> >
Subject: [EXTERNAL] Re: [WebAIM] Providing accessible names with <title>
[You don't often get email from <EMAIL REMOVED> . Learn why this is important at https://aka.ms/LearnAboutSenderIdentification ]
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.
- Next message: Yeti: "Re: Form fields in a sentence"
- Previous message: Mark Magennis: "Form fields in a sentence"
- Next message in Thread: Nick Bromley: "Re: Providing accessible names with
" - Previous message in Thread: Yeti: "Re: Providing accessible names with
" - View all messages in this Thread