Re: Focus not "obscured" to "overlapped"

• From: Laura Carlson <laura.lee.carlson@gmail.com>
• Date: Wed, 24 Aug 2022 09:10:24 -0500
• To: Alastair Campbell <acampbell@nomensa.com>
• Cc: "WCAG list (w3c-wai-gl@w3.org)" <w3c-wai-gl@w3.org>
• Message-ID: <CAOavpvee+cppbLZzGbX=jZ4QPm3nj1BUzn0hMiHGSV9Y6CXs8g@mail.gmail.com>

+1

Kind Regards,
Laura

On 8/24/22, 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
>


-- 
Laura L. Carlson

Received on Wednesday, 24 August 2022 14:10:42 UTC