Re: Focus not "obscured" to "overlapped"

+1 to this change.

From: Alastair Campbell <>
Date: Wednesday, August 24, 2022 at 8:00 AM
To: "WCAG list (" <>
Subject: Focus not "obscured" to "overlapped"
Resent-From: <>
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:

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:

Does that work? Any objections?


Received on Wednesday, 24 August 2022 12:30:08 UTC