Skip to content

2.4.11 commit from branch #274

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

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

2.4.11 commit from branch #274

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
0723001
Update 2.4.11.md
jha11y Oct 1, 2025
3d994e7
Update index.html
jha11y Oct 1, 2025
269cdb5
Merge pull request #273 from jha11y/main
jha11y Oct 7, 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
8 changes: 6 additions & 2 deletions comments/2.4.11.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,10 @@
[wcag:focus-not-obscured-minimum]
[wcag2ict:applying-sc-2-4-11-focus-not-obscured-to-non-web-documents-and-software]

Placeholder
This applies directly as written, and as described in Intent from [Understanding Success Criterion 2.4.11](https://www.w3.org/WAI/WCAG22/Understanding/focus-not-obscured-minimum.html#intent).

[issue:52]
**2.4.11 Focus Not Obscured (Minimum):** When a [user interface component](https://www.w3.org/TR/WCAG22/#dfn-user-interface-components) receives keyboard focus, the component is not entirely hidden due to author-created content.

[note:Where content in a configurable interface can be repositioned by the user, then only the initial positions of user-movable content are considered for testing and conformance of this success criterion.]

[note:Content opened by the *user* may obscure the component receiving focus. If the user can reveal the focused component without advancing the keyboard focus, the component with focus is not considered visually hidden due to author-created content.]
19 changes: 10 additions & 9 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2935,17 +2935,18 @@ <h2>Success Criterion 2.4.11 Focus Not Obscured (Minimum)</h2>
</footer>
</details>
</p>
<p>Placeholder</p>
<p>This applies directly as written, and as described in Intent from <a href="https://www.w3.org/WAI/WCAG22/Understanding/focus-not-obscured-minimum#intent">Understanding Success Criterion 2.4.11</a>.</p>
<p><strong>2.4.11 Focus Not Obscured (Minimum):</strong> When a <a href="https://www.w3.org/TR/wcag22/#dfn-user-interface-components">user interface component</a> receives keyboard focus, the component is not entirely hidden due to author-created content.</p>
<p>
<div class="note" title="Work In Progress">
<p>
<a href="https://github.com/w3c/matf/issues/52" target="_blank">
Read issue #52 on GitHub
</a>
</p>
<div class="note">
<p>Where content in a configurable interface can be repositioned by the user, then only the initial positions of user-movable content are considered for testing and conformance of this Success Criterion.</p>
</div>
</p>

</p>
<p>
<div class="note">
<p>Content opened by the <em>user</em> may obscure the component receiving focus. If the user can reveal the focused component without advancing the keyboard focus, the component with focus is not considered hidden due to author-created content.</p>
</div>
</p>
</section>

<section>
Expand Down