Re: WCAG 2.2 status - Icon Description

Charles wrote:

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


> 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.



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

Received on Monday, 13 January 2020 15:48:11 UTC