Re: Focus not "obscured" to "overlapped"

+1 to this change.

From: Alastair Campbell <acampbell@nomensa.com>
Date: Wednesday, August 24, 2022 at 8:00 AM
To: "WCAG list (w3c-wai-gl@w3.org)" <w3c-wai-gl@w3.org>
Subject: Focus not "obscured" to "overlapped"
Resent-From: <w3c-wai-gl@w3.org>
Resent-Date: Wednesday, August 24, 2022 at 7:59 AM

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