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.

Sign up for GitHub

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

Suggested additional note for focus-not-obscured #4104

Open
wants to merge 6 commits into
base: main
Choose a base branch
from
+2 −0
Open

Suggested additional note for focus-not-obscured #4104

Changes from all commits
Commits
Show all changes
6 commits
Select commit Hold shift + click to select a range
f8c93df
Suggested additional note.
alastc Oct 11, 2024
98a3c0e
Merge branch 'main' into Issue3529-Focus-not-boscured
patrickhlauke Nov 1, 2024
cc903c1
Merge branch 'main' into Issue3529-Focus-not-boscured
patrickhlauke Jan 10, 2025
f0565c0
Merge branch 'main' into Issue3529-Focus-not-boscured
patrickhlauke Jan 17, 2025
5005e62
Add clarification to new note RE component vs. indicator
kfranqueiro Jan 17, 2025
cf9b03e
will already fail -> would likely fail
kfranqueiro Jan 17, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions understanding/22/focus-not-obscured-minimum.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -31,6 +31,8 @@ <h2>Intent of Focus Not Obscured (Minimum)</h2>

<p>Another form of obscuring can occur where light boxes or other semi-opaque effects overlap the item with focus. While less than 100 percent opacity is not causing the component to be <q>entirely obscured</q>, such semi-opaque overlaps may cause a failure of <a href="../understanding/non-text-contrast.html">1.4.11 Non-text Contrast</a>. When a focus indicator can be covered by a semi-opaque component, the ability of the focus indicator to pass 1.4.11 should be evaluated (and pass) while the focus indicator is under the semi-opaque component. The intention in both situations is that the component receiving focus should never be obscured to the point a user cannot tell which item has focus.</p>

<p class="note">This criterion evaluates the focused <em>component</em>, rather than the focus <em>indicator</em>. The component itself does not include the focus indicator when checking that "the component is not entirely hidden" - unless the focus indicator is inside the component, or focus is indicated by a change to the component itself. Although users benefit from both the component and the focus indicator (if external to the component) not being obscured when tracking the focus, for the purposes of this criterion only checking the component provides a clearer metric. However, if the focus indicator is obscured, it would likely fail <a href="focus-visible">2.4.7 Focus Visible</a>.</p>

<section id="Movable">
<h3>User-movable content</h3>
<p>This SC contains a note regarding content that can be repositioned. If users can move content regions, then they can potentially position the movable content such that it obscures other content that may receive focus. In such a case, the author is only responsible for ensuring that the movable content <em>in its initial position</em> does not obscure the item receiving focus.</p>
Expand Down