Skip to content

Commit a03413d

Browse files
patrickhlaukepatrickhlauke
authored
Update F110 (#3601)
* change 2.4.12 to 2.4.11 * reformat HTML * correct duplicate id for examples Closes #3600
1 parent 82f1dee commit a03413d

File tree

1 file changed

+54
-73
lines changed

1 file changed

+54
-73
lines changed

‎techniques/failures/F110.html

Lines changed: 54 additions & 73 deletions
Original file line numberDiff line numberDiff line change
@@ -1,80 +1,61 @@
11
<html xmlns="http://www.w3.org/1999/xhtml" lang="en">
2-
<head>
3-
<title>Failure of Success Criterion 2.4.12 Focus Not Obscured (Minimum) due to a sticky footer or header completely hiding focused elements</title>
4-
5-
<link rel="stylesheet" type="text/css" href="../../css/editors.css"/>
6-
7-
</head>
8-
<body>
9-
10-
<h1>Failure of Success Criterion 2.4.12 Focus Not Obscured (Minimum) due to a sticky footer or header completely hiding focused elements</h1>
11-
12-
<section id="meta">
13-
<h2>Metadata</h2>
14-
<p id="id"></p>
15-
<p id="technology">failures</p>
16-
<p id="type">failure</p>
2+
<head>
3+
<title>Failure of Success Criterion 2.4.11 Focus Not Obscured (Minimum) due to a sticky footer or header completely hiding focused elements</title>
4+
<link rel="stylesheet" type="text/css" href="../../css/editors.css"/>
5+
</head>
6+
<body>
7+
<h1>Failure of Success Criterion 2.4.11 Focus Not Obscured (Minimum) due to a sticky footer or header completely hiding focused elements</h1>
8+
<section id="meta">
9+
<h2>Metadata</h2>
10+
<p id="id"></p>
11+
<p id="technology">failures</p>
12+
<p id="type">failure</p>
13+
</section>
14+
<section id="applicability">
15+
<h2>Applicability</h2>
16+
<p>Content using any technology which supports keyboard interfaces.</p>
17+
</section>
18+
<section id="description">
19+
<h2>Description</h2>
20+
<p>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.</p>
21+
<p>Any 'sticky' content that moves with the viewport can potentially obscure other elements on the page, including controls the user may tab to.</p>
22+
</section>
23+
<section id="examples">
24+
<h2>Examples</h2>
25+
<section class="example" id="example-1">
26+
<h3>Sticky footer</h3>
27+
<p>A Web page has a sticky footer, an element that stays visible at the bottom of the viewport as the user scrolls the page. The footer is tall enough to completely cover the element in focus as a user tabs down the page.</p>
1728
</section>
18-
19-
<section id="applicability">
20-
<h2>Applicability</h2>
21-
<p>Content using any technology which supports keyboard interfaces.</p>
22-
</section>
23-
<section id="description">
24-
<h2>Description</h2>
25-
<p>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.</p>
26-
27-
<p>Any 'sticky' content that moves with the viewport can potentially obscure other elements on the page, including controls the user may tab to.</p>
29+
<section class="example" id="example-2">
30+
<h3>Sticky header</h3>
31+
<p>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.</p>
2832
</section>
29-
30-
<section id="examples">
31-
<h2>Examples</h2>
32-
33-
<section class="example" id="example-1">
34-
<h3>Sticky footer</h3>
35-
<p>A Web page has a sticky footer, an element that stays visible at the bottom of the viewport as the user scrolls the page. The footer is tall enough to completely cover the element in focus as a user tabs down the page.</p>
36-
37-
</section>
38-
39-
<section class="example" id="example-1">
40-
<h3>Sticky header</h3>
41-
<p>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.</p>
42-
43-
</section>
44-
33+
</section>
34+
<section id="tests">
35+
<h2>Tests</h2>
36+
<section class="test-procedure">
37+
<h3>Procedure</h3>
38+
<p>Tab through the links and controls on the page. Both progressing down through the page, and back up:</p>
39+
<ol>
40+
<li>Check whether the focused element is completely obscured by other content</li>
41+
</ol>
4542
</section>
46-
47-
48-
<section id="tests">
49-
<h2>Tests</h2>
50-
51-
<section class="test-procedure">
52-
<h3>Procedure</h3>
53-
<p>Tab through the links and controls on the page. Both progressing down through the page, and back up:</p>
54-
<ol>
55-
<li>Check whether the focused element is completely obscured by other content</li>
56-
</ol>
57-
58-
</section>
59-
<section class="test-results">
60-
<h3>Expected Results</h3>
61-
62-
<ul>
63-
<li>If #1 is true, then this failure condition applies and the content fails the Success Criterion.</li>
64-
</ul>
65-
</section>
66-
</section>
67-
<section id="related">
68-
<h2>Related Techniques</h2>
69-
<ul>
70-
</ul>
71-
</section>
72-
<section id="resources">
73-
<h2>Resources</h2>
43+
<section class="test-results">
44+
<h3>Expected Results</h3>
7445
<ul>
46+
<li>If #1 is true, then this failure condition applies and the content fails the Success Criterion.</li>
7547
</ul>
7648
</section>
77-
</body>
78-
79-
</html>
80-
49+
</section>
50+
<section id="related">
51+
<h2>Related Techniques</h2>
52+
<ul>
53+
</ul>
54+
</section>
55+
<section id="resources">
56+
<h2>Resources</h2>
57+
<ul>
58+
</ul>
59+
</section>
60+
</body>
61+
</html>

0 commit comments

Comments
 (0)