RE: Focus not "obscured" to "overlapped"


From: Alastair Campbell <>
Sent: Wednesday, August 24, 2022 5:59 AM
To: WCAG list ( <>
Subject: [External] : Focus not "obscured" to "overlapped"

Hi everyone,

The last (very last, I hope) potentially normative issue on WCAG 2.2 is:<;!!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:<;!!ACWV5N9M2RV99hQ!LHMH-fMUUfDKr-P8itej93ds5mRxu5CUDxAk0i4B9hvLKtQQHXHK6EsKr7U31hHb9e-RHQ5omwDSwAI1DeCxbA$>

Does that work? Any objections?


Received on Wednesday, 24 August 2022 16:23:03 UTC