W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > July to September 2022

Focus not "obscured" to "overlapped"

From: Alastair Campbell <acampbell@nomensa.com>
Date: Wed, 24 Aug 2022 11:58:43 +0000
To: "WCAG list (w3c-wai-gl@w3.org)" <w3c-wai-gl@w3.org>
Message-ID: <PR3PR09MB53475300AFD3B22D68F2C968B9739@PR3PR09MB5347.eurprd09.prod.outlook.com>
Hi everyone,

The last (very last, I hope) potentially normative issue on WCAG 2.2 is:
https://github.com/w3c/wcag/issues/2583

Summary: Is it leaving a hole that the component/indicator could be behind a semi-opaque layer?

If so, should we change the SC to talk about overlapping instead of obscuring?

E.g. When a <a>user interface component</a> receives keyboard focus, the component is not entirely overlapped by author-created content.

That means opacity doesn’t figure into the scope, if it overlaps it overlaps.

That change is implemented in:
https://github.com/w3c/wcag/pull/2634/files

Does that work? Any objections?

-Alastair
Received on Wednesday, 24 August 2022 11:59:36 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 24 August 2022 11:59:38 UTC