Technique F110:Failure of Success Criterion 2.4.11 due to a sticky footers or headers hiding focused elements
Description
The objective of this failure is to avoid situations in which people using a keyboard interface (e.g. tabbing through links and controls) cannot see where the indicator is due to other authored content.
Any 'sticky' content that moves with the viewport can potentially obscure other elements on the page, including controls the user may tab to.
Examples
Example 2: Sticky header
A Web page has a sticky header, an element that stays visible at the top of the viewport as the user scrolls the page. The header is tall enough to completely cover the element in focus as a user tabs up the page.
Applicability
Content using any technology which supports keyboard interfaces.
Tests
Procedure
Tab through the links and controls on the page. Both progressing down through the page, and back up:
- Check whether the focused element is completely obscured by other content
Expected Results
- If #1 is true, then this failure condition applies and the content fails the Success Criterion.