Re: Focus not "obscured" to "overlapped"

+1

---
Best,

Todd Libby

On Wed, Aug 24, 2022 at 04:58, Alastair Campbell <acampbell@nomensa.com> wrote:

> 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