39 lines
1.6 KiB
Markdown
39 lines
1.6 KiB
Markdown
[Back to 2 Operable index](index.html)
|
|
|
|
# 2.4.11 Focus Not Obscured (Minimum)
|
|
|
|
- Level: AA
|
|
- Guideline: 2.4 Navigable
|
|
- Principle: 2 Operable
|
|
|
|
## What it is
|
|
|
|
When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content.
|
|
|
|
## How to test
|
|
|
|
- Check: When a user interface component receives keyboard focus, the component is not entirely hidden due to author-created content.
|
|
- Use the sufficient techniques below as acceptable methods when applicable.
|
|
- Confirm none of the common failures apply.
|
|
|
|
## Sufficient techniques (W3C)
|
|
|
|
- C43: Using CSS scroll-padding to un-obscure content
|
|
|
|
## Common failures (W3C)
|
|
|
|
- F110: Failure of Success Criterion 2.4.11 Focus Not Obscured (Minimum) due to a sticky footer or header completely hiding focused elements
|
|
|
|
## Notes
|
|
|
|
- Note 1: 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 2: 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.
|
|
|
|
## Resources
|
|
|
|
- WCAG 2.2 SC: https://www.w3.org/TR/WCAG22/#focus-not-obscured-minimum
|
|
- Understanding: https://www.w3.org/WAI/WCAG22/Understanding/focus-not-obscured-minimum.html
|
|
- Quick reference: https://www.w3.org/WAI/WCAG22/quickref/?versions=2.2#focus-not-obscured-minimum
|
|
|
|
[Back to 2 Operable index](index.html)
|