-
Notifications
You must be signed in to change notification settings - Fork 3
/
Copy path2020-07-15-prototype-failure.html
520 lines (471 loc) · 25.5 KB
/
2020-07-15-prototype-failure.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
<!DOCTYPE html>
<html dir="ltr" lang="en">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width,initial-scale=1" />
<title>Prototype: Technique document| W3C WAI</title>
<link rel="stylesheet" href="https://w3.org/WAI/assets/css/style.css?1573220675560713000" />
<link rel="stylesheet" href="https://w3.org/WAI/atag/report-tool/build/bundle.css" />
<link rel="stylesheet" href="styles.css" />
<script type="text/javascript" async="" defer="" src="//www.w3.org/analytics/piwik/piwik.js"></script>
<script defer="" src="/WAI/atag/report-tool/build/bundle.js"></script>
<script src="https://cdnjs.cloudflare.com/ajax/libs/prism/1.20.0/prism.min.js"></script>
<link rel="stylesheet" href="/a11y-light.css" />
</head>
<body>
<header id="site-header" class="default-grid with-gap">
<div class="tool-header">
<span class="tool-header-name">WCAG 2.1: Techniques</span>
<div class="tool-header-logo">
<a href="http://w3.org/">
<img alt="W3C" src="https://w3.org/WAI/atag/report-tool/images/w3c.svg" width="92" height="44" />
</a>
<a href="http://w3.org/WAI/">
<img alt="Web Accessibility Initiative" src="https://w3.org//WAI/atag/report-tool/images/wai.svg" />
</a>
</div>
</div>
</header>
<main>
<div id="conformance-tool" class="default-grid leftcol">
<!-- app 'renders' here -->
<div style="display: none;" aria-hidden="true" data-svnav-router="0"></div>
<nav class="nav svelte-3wzt7m" aria-label="Steps">
<ul class="svelte-3wzt7m">
<li class="nav__item">
<a href="2020-10-13-all.html">All Techniques</a>
</li>
<li class="nav__item">
<a href="alt-index.html">All WCAG 2.1 Guidance</a>
<button style="display: inline" type="button" data-tooltip-content="#explain-supporting-documents">
<span class="visuallyhidden">Explain rule types</span>
<span aria-hidden="true" class="more-info__icon">
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 400 450" style="width: 1em">
<path fill="currentColor" d="M256 344v-40c0-4.5-3.5-8-8-8h-24v-128c0-4.5-3.5-8-8-8h-80c-4.5 0-8 3.5-8 8v40c0 4.5 3.5 8 8 8h24v80h-24c-4.5 0-8 3.5-8 8v40c0 4.5 3.5 8 8 8h112c4.5 0 8-3.5 8-8zM224 120v-40c0-4.5-3.5-8-8-8h-48c-4.5 0-8 3.5-8 8v40c0 4.5 3.5 8 8 8h48c4.5 0 8-3.5 8-8zM384 224c0 106-86 192-192 192s-192-86-192-192 86-192 192-192 192 86 192 192z"></path>
</svg>
</span>
</button>
<div id="explain-supporting-documents" hidden>
<p>WCAG comes with a number of supporting documents, including Techniques and Understanding documents.</p>
<p>See also: <a href="https://www.w3.org/WAI/standards-guidelines/wcag/#whatis2">What is in the WCAG 2 Documents</a></p>
</div>
</li>
<li class="nav__item">
<a href="#">About Techniques</a>
</li>
</ul>
</nav>
<section class="app-content svelte-1ecbihu" aria-label="Main content">
<h1 style="max-width: 20em"><span style="display: block; font-size: .5em; margin-bottom: 0.25em;">Failure F2, due to </span> Using changes in text presentation to convey information without using the appropriate markup or text </h1>
<aside class="box">
<header class="box-h box-h-icon">
<svg focusable="false" aria-hidden="true" class="icon-warning "><use xlink:href="icons.svg#icon-warning"></use></svg> Failure
</header>
<div class="box-i">
<p>This technique shows a way to <strong>fail</strong> WCAG criterion <a href="#"><strong>1.3.1 Info and relationships</strong></a>.</p>
</div>
</aside>
<section id="description">
<h2>Description</h2>
<p>This document describes a failure that occurs when a change in the appearance of text conveys meaning without using appropriate semantic markup. This failure also applies to images of text that are not enclosed in the appropriate semantic
markup.
</p>
</section>
<section id="examples">
<h2>Examples</h2>
<section class="example" id="example-1-a-list-showing-steps-in-a-sequence-">
<section class="example" id="example-1-using-css-to-style-the-p-element-to-look-like-a-heading">
<h3>Example 1: Using CSS to style the <code class="el">p</code> element to look like a heading
</h3>
<p>The author intended to make a heading but didn't want the look of the default HTML heading. So they used CSS to style the P element to look like a heading and they called it a heading. But they failed to use the proper HTML
heading element. Therefore, the Assisitive Technology could not distinguish it as a heading.
</p><pre xml:space="preserve"> <style type="text/css">
.heading1{
font-family: Times, serif;
font-size:200%;
font-weight:bold;
}
</style>
<p class="heading1">Introduction</p>
<p>This introduction provides detailed information about how to use this
........
</p>
</pre>
<div class="note">
<div role="heading" class="note-title marker" aria-level="4">Note</div>
<div>
<p>In this case, the proper approach would be to use CSS to style the <code class="el">H1</code> element in HTML.
</p>
</div>
</div>
</section>
<section class="example" id="example-2-images-of-text-used-as-headings-where-the-images-are-not-marked-up-with-heading-tags">
<h3>Example 2: Images of text used as headings where the images are not marked up with heading tags
</h3>
<p>Chapter1.gif is an image of the words, "Chapter One" in a Garamond font sized at 20 pixels. This is a failure because at a minimum the img element should be enclosed within a header element. A better solution would be to eliminate
the image and to enclose the text within a header element which has been styled using CSS.
</p><pre xml:space="preserve"><img src="Chapter1.gif" alt="Chapter One">
<p>Once upon a time in the land of the Web.....
</p>
</pre></section>
<section class="example" id="example-3-using-css-to-visually-emphasize-a-phrase-or-word-without-conveying-that-emphasis-semantically">
<h3>Example 3: Using CSS to visually emphasize a phrase or word without conveying that emphasis semantically
</h3>
<p>The following example fails because the information conveyed by using the CSS font-weight property to change to a bold font is not conveyed through semantic markup or stated explicitly in the text.
</p>
<p>Here is a CSS class to specify bold:</p><pre xml:space="preserve">.yell {
font-weight:bold;
text-transform: uppercase;
}
</pre>
<p>And here is the corresponding HTML:</p><pre xml:space="preserve"><p>
"I said, <span class="yell">no</span>, not before dinner!",
was the exasperated response when Timmy asked his mother for the
fourth time for an ice cream cone.
</p>
</pre></section>
<section class="example" id="example-4-contact-information-using-a-definition-list">
<h3>Example 4: Contact information using a definition list</h3>
<p>This example uses a defintion list to mark up pairs of related items. The pairs themselves are a logically related list. Since browsers lack wide support for CSS styling on definition list elements, span elements have been
included in the markup for styling purposes only, and are not required:
</p><pre xml:space="preserve"><code class="language-markup"><dl>
<dt><span>name:</span></dt><dd><span>John Doe</span></dd>
<dt><span>tel:</span></dt><dd><span>01-2345678</span></dd>
<dt><span>fax:</span></dt><dd><span>02-3456789</span></dd>
<dt><span>email:</span></dt><dd><span>[email protected]</span></dd>
</dl></code>
</pre>
<p>The following CSS styling can be used to format each paired item in the list on its own line, as well as giving a table-like layout:
</p><pre xml:space="preserve"><code class="language-css">dt, dd{float: left;margin: 0;padding: 0;}
dt{clear:both;font-weight: bold}
dt span{display: inline-block; width: 70px;}
dd span{display: inline-block; margin-right: 5px;}</code>
</pre>
<p class="working-example">This is shown in the <a href="../../working-examples/definition-list-contact-info/">working example of Contact information using a definition list</a>
</p>
</section>
<section class="example" id="example-5-using-lists-to-group-links">
<h3>Example 5: Using lists to group links</h3>
<p>In this example the links are grouped using the <code class="el">ul</code> and <code class="el">li</code> elements.
</p><pre xml:space="preserve"><code class="language-markup"><a name="categories" id="categories"></a><h2>Product Categories</h2>
<ul class="navigation">
<li><a href="kitchen.html">Kitchen</a></li>
<li><a href="bedbath.html">Bed &amp; Bath</a></li>
<li><a href="dining.html">Fine Dining</a></li>
<li><a href="lighting.html">Lighting</a></li>
<li><a href="storage.html">Storage</a><li>
</ul> </code></pre>
<p>CSS can be used to style the list elements, so this technique can be used with a variety of visual appearances.
</p>
<p>Here is a style that removes the list bullets and the left padding that creates the indent and flows the individual list elements horizontally.
</p><pre xml:space="preserve"><code class="language-css">ul.navigation {
list-style: none;
padding: 0;
}
ul.navigation li {
display: inline;
}</code></pre>
<p>This style removes the list bullets and the left padding and displays the items in a floating block.
</p><pre xml:space="preserve"><code class="language-css">ul.navigation {
list-style: none;
padding: 0;
}
ul.navigation li {
display: block;
float: left;
}</code></pre></section>
</section>
<section id="tests">
<h2>Tests</h2>
<section class="procedure" id="procedure">
<h3>Procedure</h3>
<ol>
<li>
<p>For images of text:</p>
<ol>
<li>Check if any images of text are used to convey structural information of the document.</li>
<li>Check that the proper semantic structure (e.g., HTML headings) is used with the text to convey the information.
</li>
</ol>
</li>
<li>
<p>For styled text that conveys information:</p>
<ol>
<li>Check if there is any styled text that conveys structural information.</li>
<li>Check that in addition to styling, the proper semantic structure is used with the text to convey the information.
</li>
</ol>
</li>
</ol>
</section>
<section class="results" id="expected-results">
<h3>Expected Results</h3>
<ul>
<li>If check #1.1 is true, then #1.2 is true.</li>
<li>If check #2.1 is true, then #2.2 is true.</li>
</ul>
</section>
</section>
</section>
</section>
<aside class="your-report svelte-60ir8u your-report--expanded sidebar" tabindex="-1">
<style>
.sidebar ul {
padding: 0;
}
.sidebar li {
margin-left: 1em;
}
</style>
<h2 style="margin-top: 0">About this page</h2>
<p><em>Failure Techniques</em> show ways in which criteria are considered “not met”.</p>
<style>
dd {
margin-left: 0!important;
}
</style>
<dl>
<dt>Type of technique
<button style="display: inline" type="button" data-tooltip-content="#explain-types-of-techniques">
<span class="visuallyhidden">Explain types of techniques</span>
<span aria-hidden="true" class="more-info__icon">
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 400 450" style="width: 1em">
<path fill="currentColor" d="M256 344v-40c0-4.5-3.5-8-8-8h-24v-128c0-4.5-3.5-8-8-8h-80c-4.5 0-8 3.5-8 8v40c0 4.5 3.5 8 8 8h24v80h-24c-4.5 0-8 3.5-8 8v40c0 4.5 3.5 8 8 8h112c4.5 0 8-3.5 8-8zM224 120v-40c0-4.5-3.5-8-8-8h-48c-4.5 0-8 3.5-8 8v40c0 4.5 3.5 8 8 8h48c4.5 0 8-3.5 8-8zM384 224c0 106-86 192-192 192s-192-86-192-192 86-192 192-192 192 86 192 192z"></path>
</svg>
</span>
</button>
<div id="explain-types-of-techniques" hidden>
<p>There are different types of techniques:</p>
<ul>
<li>Sufficient - reliable ways to meet a WCAG Criterion</li>
<li>Advisory - suggested ways to improve accessibility</li>
<li>Failure - things that cause accessibility barriers and fail specific success criteria</li>
</ul>
<p>Note: all techniques are “informative”, that is, you do not have to use them.</p>
</div>
</dt>
<dd>Failure</dd>
<dt>Example of a failure of</dt>
<dd><a href="https://www.w3.org/WAI/WCAG21/quickref/?versions=2.1#info-and-relationships">1.3.1 Info and relationships</a></dd>
<dt>Related test rules
<button style="display: inline" type="button" data-tooltip-content="#explain-test-rules">
<span class="visuallyhidden">Explain test rules</span>
<span aria-hidden="true" class="more-info__icon">
<svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 400 450" style="width: 1em">
<path fill="currentColor" d="M256 344v-40c0-4.5-3.5-8-8-8h-24v-128c0-4.5-3.5-8-8-8h-80c-4.5 0-8 3.5-8 8v40c0 4.5 3.5 8 8 8h24v80h-24c-4.5 0-8 3.5-8 8v40c0 4.5 3.5 8 8 8h112c4.5 0 8-3.5 8-8zM224 120v-40c0-4.5-3.5-8-8-8h-48c-4.5 0-8 3.5-8 8v40c0 4.5 3.5 8 8 8h48c4.5 0 8-3.5 8-8zM384 224c0 106-86 192-192 192s-192-86-192-192 86-192 192-192 192 86 192 192z"></path>
</svg>
</span>
</button>
<div id="explain-test-rules" hidden>WCAG Success Criteria interpreted as test rules, created by the ACT Task Force.</div>
</dt>
<dd><a href="2020-07-15-prototype-act.html">HTML page has title</a></dd>
<dt>Related Techniques</dt>
<dd><a href="https://www.w3.org/WAI/WCAG21/Techniques/html/H40">H40: Using description lists</a></dd>
</dl>
<h3>Other sources</h3>
<p style="margin-top: -.5em; margin-bottom: 1.5em;"><em><small>No endorsement implied.</small></em></p>
<ul>
<li>HTML 4.01 <a href="https://www.w3.org/TR/html4/struct/lists.html#h-10.2">Unordered lists (UL), ordered lists (OL), and list items (LI)</a>
</li>
<li>HTML 4.01 <a href="https://www.w3.org/TR/html4/struct/lists.html#h-10.3">Definition lists: the DL, DT, and DD elements</a>
</li>
</ul>
</aside>
</div>
</main>
<div class="default-grid">
<aside class="box box-icon box-space-above" id="helpimprove" style="-ms-grid-column: 2; -ms-grid-column-span: 8; grid-column: 2 / 8;">
<header class="box-h box-h-icon box-h-space-above box-h-icon">
<svg focusable="false" aria-hidden="true" class="icon-comments">
<use
xlink:href="/WAI/atag/report-tool/images/icons.svg#icon-comments"
></use>
</svg>
<h2>Help improve this page</h2>
</header>
<div class="box-i">
<p>
Please share your ideas, suggestions, or comments via e-mail to the publicly-archived list
<a href="mailto:[email protected]?subject=[en]%20Accessibility%20Fundamentals%20Overview">[email protected]</a
>
or via GitHub.
</p>
<div class="button-group">
<a
href="mailto:[email protected]?subject=[en]%20ATAG%20Report%20Tool&body=[put%20comment%20here...]"
class="button"
><span>E-mail</span></a
>
<a
href="https://github.com/w3c/wai-atag-report-tool/"
class="button"
><span>Fork & Edit on GitHub</span></a
><a
href="https://github.com/w3c/wai-atag-report-tool/issues/new"
class="button"
><span>New GitHub Issue</span></a
>
</div>
</div>
<div></div>
</aside>
</div>
<footer
id="wai-site-footer"
class="page-footer default-grid"
aria-label="Page"
>
<div
class="inner"
style="-ms-grid-column: 2; -ms-grid-column-span: 8; grid-column: 2 / 8;"
>
<p><strong>Date:</strong> Published 29 June 2020.</p>
<p>
<strong>Developer and Editor</strong>:
<a href="https://www.w3.org/People/hidde/">Hidde de Vries</a>.
<strong>Project Lead</strong>:
<a href="https://www.w3.org/People/shadi/">Shadi Abou-Zahra</a>.
<strong>Contributors</strong>:
<a href="https://www.w3.org/People/Shawn/">Shawn Lawton Henry</a>, Eric Eggert, Kevin White, and Daniel Montalvo.
<a href="/WAI/atag/report-tool/acknowledgements">Acknowledgements</a> lists additional contributors.
</p>
<p>
Developed by the Education and Outreach Working Group (<a href="http://www.w3.org/WAI/EO/">EOWG</a
>) with support from the
<a href="https://www.w3.org/WAI/about/projects/wai-guide/"
>WAI-Guide</a
>
project funded by the European Commission (EC) under the Horizon 2020
program (Grant Agreement 822245).
</p>
</div>
</footer>
<footer class="site-footer grid-4q" aria-label="Site">
<div class="q1-start q3-end about">
<div>
<p>
<a
class="largelink"
href="https://w3.org/WAI/"
dir="auto"
translate="no"
lang="en"
>W3C Web Accessibility Initiative (WAI)</a
>
</p>
<p>
Strategies, standards, and supporting resources to make the Web
accessible to people with disabilities.
</p>
</div>
<div class="social" dir="auto" translate="no" lang="en">
<ul>
<li>
<a href="https://twitter.com/w3c_wai"
><svg focusable="false" aria-hidden="true" class="icon-twitter">
<use
xlink:href="/WAI/atag/report-tool/images/icons.svg#icon-twitter"
></use>
</svg>
Twitter</a
>
</li>
<li>
<a href="https://w3.org/WAI/feed.xml"
><svg focusable="false" aria-hidden="true" class="icon-rss">
<use
xlink:href="/WAI/atag/report-tool/images/icons.svg#icon-rss"
></use>
</svg>
Feed</a
>
</li>
<li>
<a
href="https://www.youtube.com/channel/UCU6ljj3m1fglIPjSjs2DpRA/playlistsv"
><svg focusable="false" aria-hidden="true" class="icon-youtube">
<use
xlink:href="/WAI/atag/report-tool/images/icons.svg#icon-youtube"
></use>
</svg>
YouTube</a
>
</li>
<li>
<a href="https://w3.org/WAI/news/subscribe/" class="button"
>Get News in Email</a
>
</li>
</ul>
</div>
<div dir="auto" translate="no" lang="en">
<p>
Copyright © 2019 W3C <sup>®</sup> (<a
href="https://www.csail.mit.edu/"
><abbr title="Massachusetts Institute of Technology">MIT</abbr></a
>,
<a href="https://www.ercim.eu/"
><abbr
title="European Research Consortium for Informatics and Mathematics"
>ERCIM</abbr
></a
>, <a href="https://www.keio.ac.jp/">Keio</a>,
<a href="https://ev.buaa.edu.cn">Beihang</a>)
<a href="https://w3.org/WAI/about/using-wai-material/">Permission to Use WAI Material</a
>.
</p>
</div>
</div>
<div dir="auto" translate="no" class="q4-start q4-end" lang="en">
<ul style="margin-bottom: 0;">
<li>
<a href="https://w3.org/WAI/about/contacting/">Contact WAI</a>
</li>
<li><a href="https://w3.org/WAI/sitemap/">Site Map</a></li>
<li><a href="https://w3.org/WAI/news/">News</a></li>
<li><a href="https://w3.org/WAI/sitemap/#archive">Archive</a></li>
<li>
<a href="https://w3.org/WAI/about/accessibility-statement/">Accessibility Statement</a
>
</li>
<li><a href="https://w3.org/WAI/translations/"> Translations</a></li>
<li><a href="https://w3.org/WAI/roles/">Resources for Roles</a></li>
</ul>
</div>
</footer>
<script src="https://unpkg.com/@popperjs/core@2/dist/umd/popper.min.js"></script>
<script src="https://unpkg.com/tippy.js@6/dist/tippy-bundle.umd.js"></script>
<script>
var tooltips = document.querySelectorAll('[data-tooltip-content]');
for (i = 0, length = tooltips.length; i < length; i++) {
var contentPointer = tooltips[i].getAttribute('data-tooltip-content');
var content = document.querySelector(contentPointer).innerHTML;
tippy(tooltips[i], {
content: content,
allowHTML: true,
interactive: true,
});
}
</script>
<style>
[data-tooltip-content] {
padding: 0;
background: none;
border: 0;
color: black;
font-size: inherit;
vertical-align: middle;
}
[data-tooltip-content]:hover {
background: none;
color: var(--light-blue);
}
[data-tippy-root] {
padding: 0 2em;
}
dt div {
font-weight: normal;
}
</style>
</body>
</html>