-
Notifications
You must be signed in to change notification settings - Fork 285
/
Copy pathname-role-value.html
214 lines (213 loc) · 9.14 KB
/
name-role-value.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
<!DOCTYPE html>
<html lang="en" xml:lang="en" xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta charset="UTF-8"/>
<title>Understanding Name, Role, Value</title>
<link rel="stylesheet" type="text/css" href="../../css/sources.css" class="remove"/>
</head>
<body>
<h1>Understanding Name, Role, Value</h1>
<section id="brief">
<h2>In brief</h2>
<dl>
<dt>Goal</dt><dd>People using assistive technology understand all components.</dd>
<dt>What to do</dt><dd>Give components correct names, roles, states, and values.</dd>
<dt>Why it's important</dt><dd>Assistive technology only works well when code is done properly.</dd>
</dl>
</section>
<section id="intent">
<h2>Intent of Name, Role, Value</h2>
<p>The intent of this Success Criterion is to ensure that Assistive Technologies (AT)
can gather appropriate information about, activate (or set) and keep up to date on the status of
user interface controls in the content.
</p>
<p>When standard controls from accessible technologies are used, this process is straightforward.
If the user interface elements are used according to specification the conditions
of this provision will be met. (See examples of Success Criterion 4.1.2 below)
</p>
<p>If custom controls are created, however, or interface elements are programmed (in
code or script) to have a different role and/or function than usual, then additional
measures need to be taken to ensure that the controls provide important and appropriate information
to assistive technologies and allow themselves to be controlled by assistive technologies.
</p>
<p>What roles and states are appropriate to convey to assistive technology will depend
on what the control represents. Specifics about such information are defined by other
specifications, such as <a href="https://www.w3.org/TR/wai-aria/">WAI-ARIA</a>, or the
relevant platform standards. Another factor to consider is whether there is sufficient
<a>accessibility support</a> with assistive technologies to convey the information as specified.
</p>
<p>A particularly important state of a user interface control is whether or not it has
focus. The focus state of a control can be programmatically determined, and notifications
about change of focus are sent to user agents and assistive technology. Other examples
of user interface control states are whether or not a checkbox or radio button has
been selected, or whether a collapsible tree view or accordion is expanded or collapsed.
</p>
<div class="note">
<p>Success Criterion 4.1.2 requires a programmatically determinable name for all user
interface components. Names may be visible or invisible. Occasionally, the name needs
to be visible, in which case it is identified as a label. Refer to the definition of
name and label in the glossary for more information.
</p>
</div>
</section>
<section id="benefits">
<h2>Benefits of Name, Role, Value</h2>
<ul>
<li>Providing role, state, and value information on all user interface components enables
compatibility with assistive technology, such as screen readers, screen magnifiers,
and speech recognition software, used by people with disabilities.
</li>
</ul>
</section>
<section id="examples">
<h2>Examples of Name, Role, Value</h2>
<dl>
<dt>Accessible APIs</dt>
<dd>A Java applet uses the accessibility API defined by the language.</dd>
</dl>
</section>
<section id="resources">
<h2>Resources for Name, Role, Value</h2>
<ul>
<li>
<a href="https://www.w3.org/WAI/PF/roadmap/">Dynamic Accessible Web Content Roadmap</a>
</li>
<li>
<a href="https://www.w3.org/WAI/PF/GUI/">Role Taxonomy for Accessible Adaptable Applications</a>
</li>
<li>
<a href="https://www.w3.org/TR/wai-aria/">Web Accessibility Initiative - Accessible Rich Internet Applications (ARIA)</a>
</li>
</ul>
</section>
<section id="techniques">
<h2>Techniques for Name, Role, Value</h2>
<section id="sufficient">
<h3>Sufficient Techniques for Name, Role, Value</h3>
<section class="situation" id="name-role-value-situation-0">
<h4>Situation A: If using a standard user interface component in a markup language (e.g.,
HTML):
</h4>
<ul>
<li>
<a href="../Techniques/aria/ARIA14" class="aria"></a>
</li>
<li>
<a href="../Techniques/aria/ARIA16" class="aria"></a>
</li>
<li>
<p>
<a href="../Techniques/general/G108" class="general"></a> using technology-specific techniques below:
</p>
<ul>
<li>
<a href="../Techniques/html/H91" class="html"></a>
</li>
<li>
<a href="../Techniques/html/H44" class="html"></a>
</li>
<li>
<a href="../Techniques/html/H64" class="html"></a>
</li>
<li>
<a href="../Techniques/html/H65" class="html"></a>
</li>
<li>
<a href="../Techniques/html/H88" class="html"></a>
</li>
</ul>
</li>
</ul>
</section>
<section class="situation" id="name-role-value-situation-1">
<h4>Situation B: If using script or code to re-purpose a standard user interface component
in a markup language:
</h4>
<ul>
<li>
<p>Exposing the names and roles, allowing user-settable properties to be directly set,
and providing notification of changes using one of the following techniques:
</p>
<ul>
<li>
<a href="../Techniques/aria/ARIA16" class="aria"></a>
</li>
</ul>
</li>
</ul>
</section>
<section class="situation" id="name-role-value-situation-2">
<h4>Situation C: If using a standard user interface component in a programming technology:</h4>
<ul>
<li>
<p>
<a href="../Techniques/general/G135" class="general"></a> using technology-specific techniques below:
</p>
<ul>
<li>
<a href="../Techniques/pdf/PDF10" class="pdf"></a>
</li>
<li>
<a href="../Techniques/pdf/PDF12" class="pdf"></a>
</li>
</ul>
</li>
</ul>
</section>
<section class="situation" id="name-role-value-situation-3">
<h4>Situation D: If creating your own user interface component in a programming language:</h4>
<ul>
<li>
<p>
<a href="../Techniques/general/G10" class="general"></a> using technology-specific techniques below:
</p>
<ul>
<li>
<a href="../Techniques/aria/ARIA4" class="aria"></a>
</li>
<li>
<a href="../Techniques/aria/ARIA5" class="aria"></a>
</li>
<li>
<a href="../Techniques/aria/ARIA16" class="aria"></a>
</li>
</ul>
</li>
</ul>
</section>
</section>
<section id="advisory">
<h3>Additional Techniques (Advisory) for Name, Role, Value</h3>
</section>
<section id="failure">
<h3>Failures for Name, Role, Value</h3>
<ul>
<li>
<a href="../Techniques/failures/F59" class="failure"></a>
</li>
<li>
<a href="../Techniques/failures/F15" class="failure"></a>
</li>
<li>
<a href="../Techniques/failures/F20" class="failure"></a>
</li>
<li>
<a href="../Techniques/failures/F42" class="failure"></a>
</li>
<li>
<a href="../Techniques/failures/F68" class="failure"></a>
</li>
<li>
<a href="../Techniques/failures/F79" class="failure"></a>
</li>
<li>
<a href="../Techniques/failures/F86" class="failure"></a>
</li>
<li>
<a href="../Techniques/failures/F89" class="failure"></a>
</li>
</ul>
</section>
</section>
</body>
</html>