W3C home > Mailing lists > Public > w3c-wai-gl@w3.org > July to September 2022

Re: [EXT] Re: Focus not "obscured" to "overlapped"

From: Jennifer Strickland <jstrickland@mitre.org>
Date: Wed, 24 Aug 2022 13:23:43 +0000
To: Alastair Campbell <acampbell@nomensa.com>, "WCAG list (w3c-wai-gl@w3.org)" <w3c-wai-gl@w3.org>
Message-ID: <SA0PR09MB7002FBCB6CC7D251DFA75A95B0739@SA0PR09MB7002.namprd09.prod.outlook.com>

From: Todd Libby <toddlibby@protonmail.com>
Date: Wednesday, August 24, 2022 at 8:48 AM
To: Alastair Campbell <acampbell@nomensa.com>, WCAG list (w3c-wai-gl@w3.org) <w3c-wai-gl@w3.org>
Subject: [EXT] Re: Focus not "obscured" to "overlapped"


Todd Libby

On Wed, Aug 24, 2022 at 04:58, Alastair Campbell <acampbell@nomensa.com<mailto:acampbell@nomensa.com>> wrote:
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 13:24:03 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 24 August 2022 13:24:04 UTC