- From: Michael Livesey <mike.j.livesey@gmail.com>
- Date: Fri, 14 Jun 2024 17:01:07 +0100
- To: Ms J <ms.jflz.woop@gmail.com>
- Cc: "w3c-wai-ig@w3.org" <w3c-wai-ig@w3.org>
Received on Friday, 14 June 2024 16:01:13 UTC
The icon would be equally vague to an accessible and non-accessible user, so you wouldn't be disadvantaging accessible users. It's bad UX, but remember that WCAG is there to ensure that accessible users have the same experience as non-accessible users. It's not there to stop rubbish UX decisions. On Friday, June 14, 2024, Ms J <ms.jflz.woop@gmail.com> wrote: > Hello > If I have a button and the visible label is an icon or image which is basically very abstract and it isn't possible to infer the purpose of the control from the icon alone, but the button has a clear accessible name, does this fail 'headings and labels' please? It almost feels as though there is no label at all if the label is just a useless image or icon that does not clearly indicate the purpose of the control, in which case I even think there's an argument that it fails 'labels or instructions'. I have seen icons for say 'settings' labelled by images of animals (because this image was the company logo) which is entirely unrelated to. The accessible name was 'settings' but this doesn't fail label in name as the label is an image. > Thanks > Sarah > Sent from Outlook for iOS
Received on Friday, 14 June 2024 16:01:13 UTC