RE: Focus not "obscured" to "overlapped"

+1

From: Alastair Campbell <acampbell@nomensa.com>
Sent: Wednesday, August 24, 2022 5:59 AM
To: WCAG list (w3c-wai-gl@w3.org) <w3c-wai-gl@w3.org>
Subject: [External] : Focus not "obscured" to "overlapped"

Hi everyone,

The last (very last, I hope) potentially normative issue on WCAG 2.2 is:
https://github.com/w3c/wcag/issues/2583<https://urldefense.com/v3/__https:/github.com/w3c/wcag/issues/2583__;!!ACWV5N9M2RV99hQ!LHMH-fMUUfDKr-P8itej93ds5mRxu5CUDxAk0i4B9hvLKtQQHXHK6EsKr7U31hHb9e-RHQ5omwDSwAI1RAg8nA$>

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<https://urldefense.com/v3/__https:/github.com/w3c/wcag/pull/2634/files__;!!ACWV5N9M2RV99hQ!LHMH-fMUUfDKr-P8itej93ds5mRxu5CUDxAk0i4B9hvLKtQQHXHK6EsKr7U31hHb9e-RHQ5omwDSwAI1DeCxbA$>

Does that work? Any objections?

-Alastair