Skip to content

Commit 602926f

Browse files
patrickhlaukepatrickhlauke
authored
Add F42 as failure for 4.1.2 (#4052)
Closes #1263 (also cleans up the markup of 4.1.2 understanding, removing all unnecessary/excessive line breaks, fixes the invalid use of `</meta>`, and removes the unnecessary techniques link text which is autopopulated at publish time)
1 parent a9e49c0 commit 602926f

File tree

1 file changed

+21
-181
lines changed

1 file changed

+21
-181
lines changed

‎understanding/20/name-role-value.html

+21-181
Original file line numberDiff line numberDiff line change
@@ -1,99 +1,74 @@
11
<!DOCTYPE html>
22
<html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml">
33
<head>
4-
<meta charset="UTF-8"></meta>
4+
<meta charset="UTF-8"/>
55
<title>Understanding Name, Role, Value</title>
66
<link rel="stylesheet" type="text/css" href="../../css/sources.css" class="remove"/>
77
</head>
88
<body>
99
<h1>Understanding Name, Role, Value</h1>
10-
1110
<section id="brief">
1211
<h2>In brief</h2>
1312
<dl>
1413
<dt>Goal</dt><dd>People using assistive technology understand all components.</dd>
1514
<dt>What to do</dt><dd>Give components correct names, roles, states, and values.</dd>
16-
<dt>Why it's important</dt><dd>Assistive technology only works well when code is done properly.</dd>
15+
<dt>Why it's important</dt><dd>Assistive technology only works well when code is done properly.</dd>
1716
</dl>
18-
1917
</section>
20-
2118
<section id="intent">
2219
<h2>Intent of Name, Role, Value</h2>
23-
24-
2520
<p>The intent of this Success Criterion is to ensure that Assistive Technologies (AT)
2621
can gather appropriate information about, activate (or set) and keep up to date on the status of
2722
user interface controls in the content.
2823
</p>
29-
3024
<p>When standard controls from accessible technologies are used, this process is straightforward.
3125
If the user interface elements are used according to specification the conditions
3226
of this provision will be met. (See examples of Success Criterion 4.1.2 below)
3327
</p>
34-
3528
<p>If custom controls are created, however, or interface elements are programmed (in
3629
code or script) to have a different role and/or function than usual, then additional
3730
measures need to be taken to ensure that the controls provide important and appropriate information
3831
to assistive technologies and allow themselves to be controlled by assistive technologies.
3932
</p>
40-
4133
<p>What roles and states are appropriate to convey to assistive technology will depend
4234
on what the control represents. Specifics about such information are defined by other
4335
specifications, such as <a href="https://www.w3.org/TR/wai-aria/">WAI-ARIA</a>, or the
4436
relevant platform standards. Another factor to consider is whether there is sufficient
4537
<a>accessibility support</a> with assistive technologies to convey the information as specified.
4638
</p>
47-
4839
<p>A particularly important state of a user interface control is whether or not it has
4940
focus. The focus state of a control can be programmatically determined, and notifications
5041
about change of focus are sent to user agents and assistive technology. Other examples
5142
of user interface control states are whether or not a checkbox or radio button has
5243
been selected, or whether a collapsible tree view or accordion is expanded or collapsed.
5344
</p>
5445

55-
5646
<div class="note">
57-
5847
<p>Success Criterion 4.1.2 requires a programmatically determinable name for all user
5948
interface components. Names may be visible or invisible. Occasionally, the name needs
6049
to be visible, in which case it is identified as a label. Refer to the definition of
6150
name and label in the glossary for more information.
6251
</p>
63-
6452
</div>
65-
66-
6753
</section>
6854
<section id="benefits">
6955
<h2>Benefits of Name, Role, Value</h2>
70-
71-
7256
<ul>
73-
7457
<li>Providing role, state, and value information on all user interface components enables
7558
compatibility with assistive technology, such as screen readers, screen magnifiers,
7659
and speech recognition software, used by people with disabilities.
7760
</li>
78-
7961
</ul>
80-
8162
</section>
82-
8363
<section id="examples">
8464
<h2>Examples of Name, Role, Value</h2>
85-
8665
<dl>
8766
<dt>Accessible APIs</dt>
8867
<dd>A Java applet uses the accessibility API defined by the language.</dd>
8968
</dl>
90-
9169
</section>
92-
9370
<section id="resources">
9471
<h2>Resources for Name, Role, Value</h2>
95-
96-
9772
<ul>
9873
<li>
9974
<a href="https://www.w3.org/WAI/PF/roadmap/">Dynamic Accessible Web Content Roadmap</a>
@@ -105,270 +80,135 @@ <h2>Resources for Name, Role, Value</h2>
10580
<a href="https://www.w3.org/TR/wai-aria/">Web Accessibility Initiative - Accessible Rich Internet Applications (ARIA)</a>
10681
</li>
10782
</ul>
108-
10983
</section>
110-
11184
<section id="techniques">
11285
<h2>Techniques for Name, Role, Value</h2>
113-
114-
11586
<section id="sufficient">
11687
<h3>Sufficient Techniques for Name, Role, Value</h3>
117-
118-
11988
<section class="situation" id="name-role-value-situation-0">
120-
12189
<h4>Situation A: If using a standard user interface component in a markup language (e.g.,
12290
HTML):
12391
</h4>
124-
12592
<ul>
126-
12793
<li>
128-
12994
<a href="../Techniques/aria/ARIA14" class="aria"></a>
130-
13195
</li>
132-
13396
<li>
134-
13597
<a href="../Techniques/aria/ARIA16" class="aria"></a>
136-
13798
</li>
138-
13999
<li>
140-
141-
<p>
142-
143-
<a href="../Techniques/general/G108" class="general">Using markup features to expose the name and role, allow user-settable properties
144-
to be directly set, and provide notification of changes
145-
</a> using technology-specific techniques below:
100+
<p>
101+
<a href="../Techniques/general/G108" class="general"></a> using technology-specific techniques below:
146102
</p>
147-
148103
<ul>
149-
150104
<li>
151-
152-
<a href="../Techniques/html/H91" class="html">Using HTML form controls and links</a>
153-
105+
<a href="../Techniques/html/H91" class="html"></a>
154106
</li>
155-
156107
<li>
157-
158-
<a href="../Techniques/html/H44" class="html">Using label elements to associate text labels with form controls</a>
159-
108+
<a href="../Techniques/html/H44" class="html"></a>
160109
</li>
161-
162110
<li>
163-
164-
<a href="../Techniques/html/H64" class="html">Using the title attribute of the frame element</a>
165-
111+
<a href="../Techniques/html/H64" class="html"></a>
166112
</li>
167-
168113
<li>
169-
170-
<a href="../Techniques/html/H65" class="html">Using the title attribute to identify form controls when the label element cannot
171-
be used
172-
</a>
173-
114+
<a href="../Techniques/html/H65" class="html"></a>
174115
</li>
175-
176116
<li>
177-
178-
<a href="../Techniques/html/H88" class="html">Using (X)HTML according to spec</a>
179-
117+
<a href="../Techniques/html/H88" class="html"></a>
180118
</li>
181-
182119
</ul>
183-
184120
</li>
185-
186121
</ul>
187-
188122
</section>
189-
190123
<section class="situation" id="name-role-value-situation-1">
191-
192124
<h4>Situation B: If using script or code to re-purpose a standard user interface component
193125
in a markup language:
194126
</h4>
195-
196127
<ul>
197-
198128
<li>
199-
200129
<p>Exposing the names and roles, allowing user-settable properties to be directly set,
201130
and providing notification of changes using one of the following techniques:
202131
</p>
203-
204132
<ul>
205-
206133
<li>
207-
208134
<a href="../Techniques/aria/ARIA16" class="aria"></a>
209-
210135
</li>
211-
212136
</ul>
213-
214137
</li>
215-
216138
</ul>
217-
218139
</section>
219-
220140
<section class="situation" id="name-role-value-situation-2">
221-
222141
<h4>Situation C: If using a standard user interface component in a programming technology:</h4>
223-
224142
<ul>
225-
226143
<li>
227-
228144
<p>
229-
230-
<a href="../Techniques/general/G135" class="general">Using the accessibility API features of a technology to expose the names and roles,
231-
allow user-settable properties to be directly set, and provide notification of changes
232-
</a> using technology-specific techniques below:
233-
145+
<a href="../Techniques/general/G135" class="general"></a> using technology-specific techniques below:
234146
</p>
235-
236147
<ul>
237-
238148
<li>
239-
240149
<a href="../Techniques/pdf/PDF10" class="pdf"></a>
241-
242150
</li>
243-
244151
<li>
245-
246152
<a href="../Techniques/pdf/PDF12" class="pdf"></a>
247-
248153
</li>
249-
250154
</ul>
251-
252155
</li>
253-
254156
</ul>
255-
256157
</section>
257-
258158
<section class="situation" id="name-role-value-situation-3">
259-
260159
<h4>Situation D: If creating your own user interface component in a programming language:</h4>
261-
262160
<ul>
263-
264161
<li>
265-
266162
<p>
267-
268-
<a href="../Techniques/general/G10" class="general">Creating components using a technology that supports the accessibility API features
269-
of the platforms on which the user agents will be run to expose the names and roles,
270-
allow user-settable properties to be directly set, and provide notification of changes
271-
</a> using technology-specific techniques below:
272-
163+
<a href="../Techniques/general/G10" class="general"></a> using technology-specific techniques below:
273164
</p>
274-
275165
<ul>
276-
277166
<li>
278-
279167
<a href="../Techniques/aria/ARIA4" class="aria"></a>
280-
281168
</li>
282-
283169
<li>
284-
285170
<a href="../Techniques/aria/ARIA5" class="aria"></a>
286-
287171
</li>
288-
289172
<li>
290-
291173
<a href="../Techniques/aria/ARIA16" class="aria"></a>
292-
293174
</li>
294-
295175
</ul>
296-
297176
</li>
298-
299177
</ul>
300-
301178
</section>
302-
303179
</section>
304-
305180
<section id="advisory">
306181
<h3>Additional Techniques (Advisory) for Name, Role, Value</h3>
307-
308182
</section>
309-
310183
<section id="failure">
311184
<h3>Failures for Name, Role, Value</h3>
312-
313-
314185
<ul>
315-
316186
<li>
317-
318-
<a href="../Techniques/failures/F59" class="failure">Failure due to using script to make div or span a user interface control in HTML</a>
319-
187+
<a href="../Techniques/failures/F59" class="failure"></a>
188+
</li>
189+
<li>
190+
<a href="../Techniques/failures/F15" class="failure"></a>
320191
</li>
321-
322192
<li>
323-
324-
<a href="../Techniques/failures/F15" class="failure">Failure due to implementing custom controls that do not use an accessibility API</a>
325-
193+
<a href="../Techniques/failures/F20" class="failure"></a>
326194
</li>
327-
328195
<li>
329-
330-
<a href="../Techniques/failures/F20" class="failure">Failure due to not updating text alternatives when changes to non-text content occur</a>
331-
196+
<a href="../Techniques/failures/F42" class="failure"></a>
332197
</li>
333-
334198
<li>
335-
336-
<a href="../Techniques/failures/F68" class="failure">Failure of 1.3.1 and 4.1.2 due to the association of label and user interface controls
337-
not being programmatically determinable
338-
</a>
339-
199+
<a href="../Techniques/failures/F68" class="failure"></a>
340200
</li>
341-
342201
<li>
343-
344-
<a href="../Techniques/failures/F79" class="failure">Failure of Success Criterion 4.1.2 due to the focus state of a user interface component
345-
not being programmatically determinable or no notification of change of focus state
346-
available
347-
</a>
348-
202+
<a href="../Techniques/failures/F79" class="failure"></a>
349203
</li>
350-
351204
<li>
352-
353-
<a href="../Techniques/failures/F86" class="failure">Failure of Success Criterion 4.1.2 due to not providing names for each part of a multi-part
354-
form field, such as a US telephone number
355-
</a>
356-
205+
<a href="../Techniques/failures/F86" class="failure"></a>
357206
</li>
358-
359207
<li>
360-
361-
<a href="../Techniques/failures/F89" class="failure">Failure of 2.4.4 due to using null alt on an image where the image is the only content
362-
in a link
363-
</a>
364-
208+
<a href="../Techniques/failures/F89" class="failure"></a>
365209
</li>
366-
367210
</ul>
368-
369211
</section>
370-
371212
</section>
372-
373213
</body>
374214
</html>

0 commit comments

Comments
 (0)