Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Focus Not Obscured (Enhanced) should permit opaque overlays #3193

Closed
bruce-usab opened this issue May 16, 2023 · 1 comment · Fixed by #3195 or #3194
Closed

Focus Not Obscured (Enhanced) should permit opaque overlays #3193

bruce-usab opened this issue May 16, 2023 · 1 comment · Fixed by #3195 or #3194

Comments

@bruce-usab
Copy link
Contributor

          > Should (Enhanced) version be so tolerant of opaque overlay?

Actually, @bruce-usab, on re-reading the Enhanced normative text, I do not believe that a lightbox should be considered to fail this criteria. The language does not use "obscured", it uses "hidden".

no part of the component is hidden by author-created content.

I don't think we can make the case that dimming something hides it. Even in the minimum version, we don't say the lightbox is failing Focus Not Obscured. We say it is likely to fail 2.4.11 Focus Appearance.

On rereading that part of the Minimum understanding document, I have some changes to suggest.

  1. Given that 2.4.11 is now a AAA, my feeling is that the language in the minimum should actually point to Non-text contrast, and
  2. the Enhanced version should point to Focus Appearance.

That gives us something appropriate to assess at each of the levels. If you agree, can you alter this PR to support that?

As part of that, you will need to remove this commit: 61dcd0c

At that point, the language for Enhanced seems fine for lightbox (assuming the link points to the AAA version of Focus Appearanced). The AA version would need to be updated.

Originally posted by @mbgower in #3163 (comment)

@bruce-usab bruce-usab changed the title > Should (Enhanced) version be so tolerant of opaque overlay? Focus Not Obscured (Enhanced) should permit opaque overlays May 16, 2023
@bruce-usab bruce-usab self-assigned this May 16, 2023
@bruce-usab
Copy link
Contributor Author

bruce-usab commented May 16, 2023

Per Tuesday call, I am opening this new issue rather than adding/editing PR #3163

As @mbgower notes above, SC 2.4.12 reads (emphasis added):

When a user interface component receives keyboard focus, no part of the component is hidden by author-created content.

The SC text clearly implies covering up or entirely hiding part of the component (with focus indicator). A (much less desirable) alternative is to tweak the SC text. That might look like:

When a user interface component receives keyboard focus, no part of the component is obscured by author-created content.

To be clear, Focus Not Obscured (Minimum) is fine as-is). The issues with 2.4.12 is that there is a tension between the non-normative name/label for the SC and its normative SC text.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment