W3C home > Mailing lists > Public > public-cognitive-a11y-tf@w3.org > January 2020

Re: WCAG 2.2 status - Visual indicators

From: Alastair Campbell <acampbell@nomensa.com>
Date: Tue, 14 Jan 2020 15:50:56 +0000
To: "public-cognitive-a11y-tf@w3.org" <public-cognitive-a11y-tf@w3.org>
Message-ID: <745B489F-97C7-40B7-B648-53D7C67C454D@nomensa.com>
Hi everyone,

I think we are all coming to the same conclusion, which is that it is very complex and needs a lot of groundwork first.

It was worth someone "taking a punt" (just having a go) to see if it worked. However, it is obviously not straightforward.

If there is ever going to be an accessibility guideline around affordances, there is certain work needed first. Going back to the original email from me that was forwarded on, we really need a systematic listing of UI components, perhaps coming from a list like this:
https://open-ui.org/analysis/component-matrix (and click the Sort by to seem common components first).

That would help to catalogue the individual components to work out what an appropriate visual indicator actually is in each case.

Also, we need to tackle the 'noise' problem. A lot of the issues Abi pointed out were that non-interactive things *did* have an indicator. The consistency approach Abi outlined probably doesn't address that, as you could have consistently *bad* elements.

Either way, creating a catalogue of controls is the first step, so I think that's better on the Silver timeline.



Received on Tuesday, 14 January 2020 15:51:03 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:24:05 UTC