forked from w3c/wcag-act
-
Notifications
You must be signed in to change notification settings - Fork 0
/
page-titled-act.html
391 lines (240 loc) · 17.1 KB
/
page-titled-act.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
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
<head>
<meta charset="UTF-8" />
<title>Understanding Success Criterion 2.4.2: Page Titled</title>
<link rel="stylesheet" type="text/css" href="https://www.w3.org/StyleSheets/TR/2016/base" />
<link rel="stylesheet" type="text/css" href="https://www.w3.org/WAI/WCAG21/Understanding/understanding.css" />
<link rel="stylesheet" type="text/css" href="https://www.w3.org/WAI/WCAG21/Understanding/slicenav.css" />
</head>
<body>
<nav>
<ul id="navigation">
<li><a href="https://www.w3.org/WAI/WCAG21/Understanding/" title="Table of Contents">Contents</a></li>
<li><a href="https://www.w3.org/WAI/WCAG21/Understanding/navigable"><abbr title="Guideline">GL</abbr>: Navigable</a></li>
<li><a href="https://www.w3.org/WAI/WCAG21/Understanding/bypass-blocks">Previous <abbr title="Success Criterion">SC</abbr>: Bypass Blocks</a></li>
<li><a href="https://www.w3.org/WAI/WCAG21/Understanding/focus-order">Next <abbr title="Success Criterion">SC</abbr>: Focus Order</a></li>
</ul>
</nav>
<nav class="navtoc">
<p>On this page:</p>
<ul id="navbar">
<li><a href="#intent">Intent</a></li>
<li><a href="#benefits">Benefits</a></li>
<li><a href="#examples">Examples</a></li>
<li><a href="#resources">Related Resources</a></li>
<li><a href="#techniques">Techniques</a></li>
<li><a href="#act-rules">ACT Rules</a></li>
<li><a href="#key-terms">Key Terms</a></li>
</ul>
</nav>
<h1>Understanding Success Criterion 2.4.2: Page Titled</h1>
<blockquote class="scquote">
<p>Success Criterion <a href="https://www.w3.org/TR/WCAG21/#page-titled" style="font-weight: bold;">2.4.2 Page Titled</a> (Level A):
<a href="#dfn-web-page">Web pages</a> have titles that describe topic or purpose.
</p>
</blockquote>
<main>
<section id="intent">
<h2>Intent</h2>
<p>The intent of this Success Criterion is to help users find content and orient themselves
within it by ensuring that each Web page has a descriptive title. Titles identify
the current location without requiring users to read or interpret page content. When
titles appear in site maps or lists of search results, users can more quickly identify
the content they need. User agents make the title of the page easily available to
the user for identifying the page. For instance, a user agent may display the page
title in the window title bar or as the name of the tab containing the page.
</p>
<p>In cases where the page is a document or a web application, the name of the document
or web application would be sufficient to describe the purpose of the page. Note that
it is not required to use the name of the document or web application; other things
may also describe the purpose or the topic of the page.
</p>
<p>
<a href="link-purpose-in-context" class="understanding">Success Criteria 2.4.4</a> and
<a href="link-purpose-link-only" class="understanding">2.4.9</a> deal with the purpose of links, many of which are links to web pages. Here also,
the name of a document or web application being linked to would be sufficient to describe
the purpose of the link. Having the link and the title agree, or be very similar,
is good practice and provides continuity between the link 'clicked on' and the web
page that the user lands on.
</p>
</section>
<section id="benefits">
<h2>Benefits</h2>
<ul>
<li>
This criterion benefits all users in allowing users to quickly and easily identify
whether the information contained in the Web page is relevant to their needs.
</li>
<li>
People with visual disabilities will benefit from being able to differentiate content
when multiple Web pages are open.
</li>
<li>
People with cognitive disabilities, limited short-term memory and reading disabilities
also benefit from the ability to identify content by its title.
</li>
<li>
This criterion also benefits people with severe mobility impairments whose mode of
operation relies on audio when navigating between Web pages.
</li>
</ul>
</section>
<section id="examples">
<h2>Examples</h2>
<ul>
<li>
<p>
<strong>An HTML Web page</strong>
</p>
<p>The descriptive title of an HTML Web page is marked up with the <title> element so
that it will be displayed in the title bar of the user agent.
</p>
</li>
<li>
<p>
<strong>A document collection.</strong>
</p>
<p>The title of
<a href="https://www.w3.org/WAI/WCAG21/Understanding/">Understanding WCAG 2.1 </a> is "Understanding WCAG 2.1."
</p>
<ul>
<li>The introduction page has the title "Introduction to Understanding WCAG 2.0."</li>
<li>Major sections of the document are pages titled "Understanding Guideline X" and "Understanding
Success Criterion X."
</li>
<li>Appendix A has the title "Glossary."</li>
<li>Appendix B has the title "Acknowledgements."</li>
<li>Appendix C has the title "References."</li>
</ul>
</li>
<li>
<p>
<strong>A Web application.</strong>
</p>
<p>
A banking application lets a user inspect his bank accounts, view past statements,
and perform transactions. The Web application dynamically generates titles for each
Web page, e.g., "Bank XYZ, accounts for John Smith" "Bank XYZ, December 2005 statement
for Account 1234-5678".
</p>
</li>
</ul>
</section>
<section id="resources">
<h2>Related Resources</h2>
<p>Resources are for information purposes only, no endorsement implied.</p>
<ul>
<li>
<a href="http://www.socialpatterns.com/search-engine-optimization/writing-better-web-page-titles/">Writing Better Web Page Titles</a> How to write titles for Web pages that will enhance search engine effectiveness.
</li>
<li>
<a href="http://redish.net/images/stories/PDF/interactions.html">Guidelines for Accessible and Usable Web Sites: Observing Users Who Work With Screen
Readers
</a>. Theofanos, M.F., and Redish, J. (2003). Interactions, Volume X, Issue 6, November-December
2003, pages 38-51,
<a href="http://dl.acm.org/citation.cfm?doid=947226.947227">http://dl.acm.org/citation.cfm?doid=947226.947227</a>
</li>
</ul>
</section>
<section id="techniques">
<h2>Techniques</h2>
<p>Each numbered item in this section represents a technique or combination of techniques
that the WCAG Working Group deems sufficient for meeting this Success Criterion. However,
it is not necessary to use these particular techniques. For information on using other
techniques, see <a href="understanding-techniques">Understanding Techniques for WCAG Success Criteria</a>, particularly the "Other Techniques" section.
</p>
<section id="sufficient">
<h3>Sufficient Techniques</h3>
<ol>
<li>
<p>
<a class="general" href="https://www.w3.org/WAI/WCAG21/Techniques/general/G88">G88: Providing descriptive titles for Web pages</a>
<strong>AND</strong> associating a title with a Web page using one of the following techniques:
</p>
<ul>
<li>
<a class="html" href="https://www.w3.org/WAI/WCAG21/Techniques/html/H25">H25: Providing a title using the title element</a>
</li>
<li>
<a class="pdf" href="https://www.w3.org/WAI/WCAG21/Techniques/pdf/PDF18">PDF18: Specifying the document title using the Title entry in the document information dictionary
of a PDF document</a>
</li>
</ul>
</li>
</ol>
</section>
<section id="advisory">
<h3>Advisory Techniques</h3>
<p>Although not required for conformance, the following additional techniques should
be considered in order to make content more accessible. Not all techniques can be
used or would be effective in all situations.
</p>
<ul>
<li>
<a class="general" href="https://www.w3.org/WAI/WCAG21/Techniques/general/G127">G127: Identifying a Web page's relationship to a larger collection of Web pages</a>
</li>
</ul>
</section>
<section id="failure">
<h3>Failures</h3>
<p>The following are common mistakes that are considered failures of this Success Criterion
by the WCAG Working Group.
</p>
<ul>
<li>
<a class="failure" href="https://www.w3.org/WAI/WCAG21/Techniques/failures/F25">F25: Failure of Success Criterion 2.4.2 due to the title of a Web page not identifying
the contents</a>
</li>
</ul>
</section>
</section>
<section id="act-rules">
<h2>ACT Rules</h2>
<p>Each numbered item in this section represents an ACT Rule that the WCAG Working Group deems appropriate for testing certain aspects of this Success Criterion. However, it is not necessary to use these particular ACT Rules to check for conformance with WCAG. For information on using ACT Rules, see <a href="understanding-act-rules.html">Understanding ACT Rules for WCAG Success Criteria</a>.</p>
<ol>
<li><a href="https://www.w3.org/WAI/standards-guidelines/act/rules/html-page-has-title-2779a5/">HTML page has title</a></li>
</ol>
</section>
<section id="key-terms">
<h2>Key Terms</h2>
<dt id="dfn-web-page">web page</dt>
<dd>
<definition xmlns="">
<p xmlns="http://www.w3.org/1999/xhtml">a non-embedded resource obtained from a single URI using HTTP plus any other resources
that are used in the rendering or intended to be rendered together with it by a <a href="#dfn-user-agent">user agent</a>
</p>
<div xmlns="http://www.w3.org/1999/xhtml" class="note">
<div role="heading" class="note-title marker" aria-level="2">Note</div>
<p>Although any "other resources" would be rendered together with the primary resource,
they would not necessarily be rendered simultaneously with each other.
</p>
</div>
<div xmlns="http://www.w3.org/1999/xhtml" class="note">
<div role="heading" class="note-title marker" aria-level="2">Note</div>
<p>For the purposes of conformance with these guidelines, a resource must be "non-embedded"
within the scope of conformance to be considered a Web page.
</p>
</div>
<p xmlns="http://www.w3.org/1999/xhtml" class="example">A Web resource including all embedded images and media.</p>
<p xmlns="http://www.w3.org/1999/xhtml" class="example">A Web mail program built using Asynchronous JavaScript and XML (AJAX). The program
lives entirely at http://example.com/mail, but includes an inbox, a contacts area
and a calendar. Links or buttons are provided that cause the inbox, contacts, or calendar
to display, but do not change the URI of the page as a whole.
</p>
<p xmlns="http://www.w3.org/1999/xhtml" class="example">A customizable portal site, where users can choose content to display from a set of
different content modules.
</p>
<p xmlns="http://www.w3.org/1999/xhtml" class="example">When you enter "http://shopping.example.com/" in your browser, you enter a movie-like
interactive shopping environment where you visually move around in a store dragging
products off of the shelves around you and into a visual shopping cart in front of
you. Clicking on a product causes it to be demonstrated with a specification sheet
floating alongside. This might be a single-page Web site or just one page within a
Web site.
</p>
</definition>
</dd>
</section>
</main>
</body>
</html>