Re: Focus not "obscured" to "overlapped"

I agree with Jon Avila that the scenario we are trying to address would be
addressed by 1.4.11 or 2.4.11. Something could be completely overlapped by
a thing that has only a small amount of opacity and still be visible to the
standards of 1.4.11 and / or 2.4.11.

*Melanie Philipp, CPACC, WAS | *Director, Services Methodology
| 540-848-5220
Deque Systems - Accessibility for Good
www.deque.com


On Wed, Aug 24, 2022 at 10:11 AM Laura Carlson <laura.lee.carlson@gmail.com>
wrote:

> +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
>
>