Re: WCAG 2.2 status - Icon Description

"

If we are requiring external toggles (or that every icon has a visible description by default), I think that is heading towards an AAA type of criteria.

Or, we could accept that touch-screens have less interaction options available and only require the focus/hover methods for showing (initially hidden) descriptions.

 "


We might take a look at splitting the SC, a AA (hover / focus) and a AAA (more)?!

________________________________
From: Alastair Campbell <acampbell@nomensa.com>
Sent: Monday, January 13, 2020 4:48 PM
To: Hall, Charles (DET-MRM) <Charles.Hall@mrm-mccann.com>
Cc: WCAG list <w3c-wai-gl@w3.org>
Subject: Re: WCAG 2.2 status - Icon Description


Charles wrote:

> I am suggesting the text description accompany all instances – if those instances are flow content.

And:

> I would not promote a pattern where a user is required to interact with an

> element to understand the element.



So if all icons must have a text description available (presumably adjacent to the icon), and we cannot rely on tap, that would require another control somewhere to toggle descriptions. Unless I’m missing something, is there another method?



In which case the addition of a printer icon-link on a page would trigger the need for an extra control on that page to toggle the description visibility.



If we are requiring external toggles (or that every icon has a visible description by default), I think that is heading towards an AAA type of criteria.

Or, we could accept that touch-screens have less interaction options available and only require the focus/hover methods for showing (initially hidden) descriptions.



Cheers,



-Alastair



PS. Did you mean ‘flow content’ in HTML terms, i.e. block elements?

-----------------------------------------------------------------
ATTENTION:
The information in this e-mail is confidential and only meant for the intended recipient. If you are not the intended recipient, don't use or disclose it in any way. Please let the sender know and delete the message immediately.
-----------------------------------------------------------------

Received on Tuesday, 14 January 2020 08:05:57 UTC