-
Notifications
You must be signed in to change notification settings - Fork 125
/
index.html
527 lines (513 loc) · 28.3 KB
/
index.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
521
522
523
524
525
526
527
<!doctype html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
<head>
<meta charset="UTF-8" />
<title>Graphics Accessibility API Mappings</title>
<script src="https://www.w3.org/Tools/respec/respec-w3c" class="remove" defer="defer"></script>
<script src="../common/script/resolveReferences.js" class="remove"></script>
<script src="../common/biblio.js" class="remove" defer="defer"></script>
<link href="../common/css/mapping-tables.css" rel="stylesheet" type="text/css" />
<link href="../common/css/common.css" rel="stylesheet" type="text/css" />
<!--<link href="css/dpub-aam.css" rel="stylesheet" type="text/css"/>-->
<script class="remove">
var respecConfig = {
github: "w3c/graphics-aam",
doJsonLd: true,
// specification status (e.g., WD, LC, NOTE, etc.). If in doubt use ED.
specStatus: "ED",
//crEnd: "2012-04-30",
//perEnd: "2013-07-23",
//publishDate: "2016-08-18",
// the specifications short name, as in https://www.w3.org/TR/short-name/
shortName: "graphics-aam-1.0",
// if you wish the publication date to be other than today, set this
// publishDate: "2009-08-06",
copyrightStart: "2016",
license: "document",
// if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
// and its maturity status
//previousPublishDate: "2016-08-18",
//previousMaturity: "REC",
//prevRecURI: "https://www.w3.org/TR/2014/REC-wai-aria-implementation-20140320/",
//previousDiffURI: "https://www.w3.org/TR/2014/REC-wai-aria-implementation-20140320/",
// if there a publicly available Editors Draft, this is the link
edDraftURI: "https://w3c.github.io/graphics-aam/",
// if this is a LCWD, uncomment and set the end of its review period
// lcEnd: "2012-02-21",
// editors, add as many as you like
// only "name" is required
editors: [
{ name: "Amelia Bellamy-Royds", mailto: "amelia.bellamy.royds@gmail.com", w3cid: 75809 },
{
name: "James Nurthen",
company: "Adobe",
companyURL: "https://www.adobe.com/",
w3cid: 37155,
},
],
formerEditors: [
{
name: "Joanmarie Diggs",
url: "https://www.igalia.com",
mailto: "jdiggs@igalia.com",
company: "Igalia, S.L.",
companyURL: "https://www.igalia.com",
w3cid: 68182,
note: "until August 2023",
},
{
name: "Michael Cooper",
url: "http://www.w3.org",
mailto: "cooper@w3.org",
company: "W3C",
companyURL: "http://www.w3.org",
w3cid: 34017,
note: "until August 2023",
},
{ name: "Fred Esch", mailto: "fesch@us.ibm.com", company: "IBM Corporation", companyURL: "https://www.ibm.com/", w3cid: 73593, note: "until September 2016" },
{ name: "Richard Schwerdtfeger", mailto: "richschwer@gmail.com", company: "Knowbility", companyURL: "https://knowbility.org/", w3cid: 2460, note: "until August 2017" },
],
// authors, add as many as you like.
// This is optional, uncomment if you have authors as well as editors.
// only "name" is required. Same format as editors.
authors: [
{
name: "Amelia Bellamy-Royds",
mailto: "amelia.bellamy.royds@gmail.com",
w3cid: 75809,
},
{
name: "Fred Esch",
mailto: "fesch@us.ibm.com",
company: "IBM Corporation",
companyURL: "https://www.ibm.com/",
w3cid: 73593,
},
{
name: "Richard Schwerdtfeger",
mailto: "richschwer@gmail.com",
company: "Knowbility",
companyURL: "https://knowbility.org/",
w3cid: 2460,
},
{
name: "Doug Schepers",
mailto: "schepers@w3.org",
company: "W3C",
companyURL: "https://www.w3.org/",
w3cid: 38635,
},
],
/*
alternateFormats: [
{ uri: 'graphics-aam-diff.html',
label: "Diff from Previous Recommendation" } ,
{ uri: 'graphics-aam.ps',
label: "PostScript version" },
{ uri: 'graphics-aam.pdf',
label: "PDF version" }
],
*/
// Working group info
group: "aria",
tocIntroductory: true,
//maxTocLevel: 4,
ariaSpecURLs: {
ED: "https://w3c.github.io/aria/",
FPWD: "https://www.w3.org/TR/wai-aria-1.1/",
WD: "https://www.w3.org/TR/wai-aria-1.1/",
CR: "https://www.w3.org/TR/wai-aria-1.1/",
PR: "https://www.w3.org/TR/wai-aria-1.1/",
REC: "https://www.w3.org/TR/wai-aria-1.1/",
},
accNameURLs: {
ED: "https://w3c.github.io/accname/",
FPWD: "https://www.w3.org/TR/accname-1.1/",
WD: "https://www.w3.org/TR/accname-1.1/",
CR: "https://www.w3.org/TR/accname-1.1/",
PR: "https://www.w3.org/TR/accname-1.1/",
REC: "https://www.w3.org/TR/accname-1.1/",
},
coreMappingURLs: {
ED: "https://w3c.github.io/core-aam/",
FPWD: "https://www.w3.org/TR/core-aam-1.1/",
WD: "https://www.w3.org/TR/core-aam-1.1/",
CR: "https://www.w3.org/TR/core-aam-1.1/",
PR: "https://www.w3.org/TR/core-aam-1.1/",
REC: "https://www.w3.org/TR/core-aam-1.1/",
},
dpubModURLs: {
ED: "https://w3c.github.io/dpub-aria/",
FPWD: "https://www.w3.org/TR/dpub-aria-1.0/",
WD: "https://www.w3.org/TR/dpub-aria-1.0/",
CR: "https://www.w3.org/TR/dpub-aria-1.0/",
PR: "https://www.w3.org/TR/dpub-aria-1.0/",
REC: "https://www.w3.org/TR/dpub-aria-1.0/",
},
graphicsModURLs: {
ED: "https://w3c.github.io/graphics-aria/",
FPWD: "https://www.w3.org/TR/graphics-aria-1.0/",
WD: "https://www.w3.org/TR/graphics-aria-1.0/",
CR: "https://www.w3.org/TR/graphics-aria-1.0/",
PR: "https://www.w3.org/TR/graphics-aria-1.0/",
REC: "https://www.w3.org/TR/graphics-aria-1.0/",
},
graphicsMappingURLs: {
ED: "https://w3c.github.io/graphics-aam/",
FPWD: "https://www.w3.org/TR/graphics-aam-1.0/",
WD: "https://www.w3.org/TR/graphics-aam-1.0/",
CR: "https://www.w3.org/TR/graphics-aam-1.0/",
PR: "https://www.w3.org/TR/graphics-aam-1.0/",
REC: "https://www.w3.org/TR/graphics-aam-1.0/",
},
preProcess: [linkCrossReferences],
postProcess: [],
definitionMap: [],
xref: ["core-aam", "accname", "wai-aria", "dom", "infra"],
};
</script>
</head>
<body>
<section id="abstract">
<p>
The Graphics Accessibility API Mappings defines how <a class="termref">user agents</a> map the WAI-ARIA Graphics Module [[GRAPHICS-ARIA-1.0]] markup to platform
<a class="termref">accessibility <abbr title="Application Programming Interfaces">APIs</abbr></a
>. It is intended for user agent developers responsible for accessibility in their user agent so that they can support the accessibility of graphics such as that created for [[SVG]] or
[[HTML52]].
</p>
<p>
The implementation of this specification in user agents enables authors to produce more accessible graphics by conveying common graphics semantics to assistive technologies. It provides
Accessibility API Mapping guidance for the roles defined in the WAI-ARIA Graphics Module [[GRAPHICS-ARIA-1.0]].
</p>
<p>
The Graphics Accessibility API Mappings is part of the
<abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> suite described in the
<a href="https://www.w3.org/WAI/intro/aria.php"><abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> Overview</a>.
</p>
</section>
<section id="sotd">
<p>
This is an Editor's Draft of Graphics Accessibility API Mappings 1.0 by the <a href="https://www.w3.org/WAI/PF/svg-a11y-tf/">SVG Accessibility Task Force</a>, a joint task force of the
<a href="https://www.w3.org/WAI/ARIA/">Accessible Rich Internet Applications Working Group</a> and the <a href="https://www.w3.org/Graphics/SVG/WG/">SVG Working Group</a>. It provides guidance
for mapping roles in <a href="" class="graphics">WAI-ARIA Graphics Module</a> [[GRAPHICS-ARIA-1.0]] to accessibility APIs, and complements SVG-specific mappings in the
<a href="" class="svg-mapping">SVG Accessibility API Mappings</a> [[SVG-AAM-1.0]]. It extends <a href="" class="core-mapping">Core Accessibility Mappings 1.1</a> [[CORE-AAM-1.1]], and is part
of a suite of similar technology-specific Accessibility API Mappings specifications.
</p>
<p>Feedback on any aspect of the specification is accepted. For this publication, the SVG Accessibility Task Force particularly seeks feedback on the following questions:</p>
<ul>
<li>Are mappings of graphics features clear and appropriate?</li>
<li>Do the platform API mappings appropriately reflect the semantics defined for these roles in the WAI-ARIA Graphics Module?</li>
<li>Is the relationship of this specification to <a href="" class="core-mapping">Core Accessibility API Mappings 1.1</a> clear?</li>
<li>Is the relationship of this specification to <a href="" class="graphics">WAI-ARIA Graphics Module</a> and <a href="" class="specref">WAI-ARIA 1.1</a> clear?</li>
</ul>
<p>
To comment, <a href="https://github.com/w3c/graphics-aam/issues/new">file an issue in the W3C graphics-aam GitHub repository</a>. If this is not feasible, send email to
<a href="mailto:public-aria@w3.org?subject=Graphics%20AAM%20public%20comment">public-aria@w3.org</a> (<a href="https://lists.w3.org/Archives/Public/public-aria/">comment archive</a>).
In-progress updates to the document may be viewed in the <a href="https://w3c.github.io/graphics-aam">publicly visible editors' draft</a>.
</p>
</section>
<section id="intro" class="informative">
<h2>Introduction</h2>
<p>The Graphics Accessibility API Mappings specification provides role mappings for the roles in the WAI-ARIA Graphics Module [[GRAPHICS-ARIA-1.0]].</p>
<p>
For web documents and applications, the essential semantic information is encapsulated within the Document Object Model (<abbr title="Document Object Model">DOM</abbr>). Assistive technologies
obtain this information from the user agent, which maps elements and attributes to the platform Accessibility <abbr title="Application Programming Interface">API</abbr>.
</p>
<p>
The original suite of element semantics defined by
<abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> 1.0 only considered graphics as individual embedded images, with no interactivity or meaningful semantic structure. It was
therefore not sufficient for communicating complex graphics, such as labelled diagrams or data charts, or for interactive graphics. The WAI-ARIA Graphics Module defines a core set of three
roles that can convey the structure of a graphic. This specification defines how <a>user agents</a> should expose those roles to the <a>accessibility APIs</a> currently in use, so that the
semantic information is available to <a>assistive technologies</a> that use those APIs.
</p>
<p>
For an introduction to <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr>, see the
<a href="https://www.w3.org/WAI/intro/aria.php"><abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> Overview</a>. It is part of a set of resources that define and support the
<abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> specification, including the following documents:
</p>
<ul>
<li>
<cite><a href="https://www.w3.org/TR/wai-aria-1.1/">Accessible Rich Internet Applications (WAI-ARIA) 1.1</a></cite> [[WAI-ARIA-1.1]], a planned
<abbr title="World Wide Web Consortium">W3C</abbr> recommendation that extends the exising ARIA standard [[WAI-ARIA-1.0]]. It defines the core roles, states, and properties.
</li>
<li>
<cite><a href="https://www.w3.org/TR/graphics-aria-1.0/">WAI-ARIA Graphics Module</a></cite> [[GRAPHICS-ARIA-1.0]], a planned
<abbr title="World Wide Web Consortium">W3C</abbr> recommendation that defines graphics roles, states, and properties not included in
<cite><a href="https://www.w3.org/TR/wai-aria-1.1/">Accessible Rich Internet Applications (WAI-ARIA) 1.1</a></cite> [[WAI-ARIA-1.1]].
</li>
<li>
<cite><a href="https://www.w3.org/TR/core-aam-1.1/">Core Accessibility API Mappings</a></cite> specification [[CORE-AAM-1.1]], which expresses how
<abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> <a class="termref">roles</a>, <a class="termref">states</a>, and [=ARIA/properties=] should be supported in user agents
using platform accessibility <abbr title="Application Programming Interfaces">APIs</abbr>.
</li>
<li>
<cite><a href="https://www.w3.org/TR/svg-aam-1.0/">SVG Accessibility API Mappings</a></cite> [[SVG-AAM-1.0]], a planned <abbr title="World Wide Web Consortium">W3C</abbr> recommendation,
which expresses how <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> <a class="termref">roles</a>, <a class="termref">states</a>, and [=ARIA/properties=] should be
supported in user agents using platform accessibility <abbr title="Application Programming Interfaces">APIs</abbr>.
</li>
<li>
<cite><a href="https://www.w3.org/TR/accname-aam-1.1/">Accessible Name and Description: Computation and API Mappings 1.1</a></cite> [[ACCNAME-AAM-1.1]], which outlines the specific steps
user agents should follow in order to identify accessible names (labels) and descriptions (alternative text) for elements that are exposed to assistive technologies.
</li>
<li>
<cite
><a href="https://www.w3.org/TR/wai-aria-practices/"><abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> Authoring Practices Guide</a></cite
>
[[WAI-ARIA-PRACTICES-1.1]], a planned W3C Working Group Note, which describes how web content developers can develop accessible rich internet applications using
<abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr>. It provides detailed advice and examples directed primarily to web application developers, yet also useful to developers
of user agents and assistive technologies.
</li>
</ul>
</section>
<section class="normative" id="conformance">
<h2>Conformance</h2>
<p>
The main content of this specification is normative and defines requirements that impact conformance claims. Introductory material, appendices, sections marked as "non-normative" and their
subsections, diagrams, examples, and notes are informative (non-normative). Non-normative material provides advisory information to help interpret the guidelines but does not create
requirements that impact a conformance claim.
</p>
<p>
Normative sections provide requirements that <a class="termref">user agents</a> must follow for an implementation to conform to this specification. The keywords <em class="rfc2119">MUST</em>,
<em class="rfc2119">MUST NOT</em>, <em class="rfc2119">REQUIRED</em>, <em class="rfc2119">SHALL</em>, <em class="rfc2119">SHALL NOT</em>, <em class="rfc2119">SHOULD</em>,
<em class="rfc2119">RECOMMENDED</em>, <em class="rfc2119">MAY</em>, and <em class="rfc2119">OPTIONAL</em> in this document are to be interpreted as described in
<cite><a href="http://www.rfc-editor.org/rfc/rfc2119.txt">Keywords for use in RFCs to indicate requirement levels</a></cite> [[!RFC2119]]. RFC-2119 keywords are formatted in uppercase and
contained in an element with <code>class="rfc2119"</code>. When the keywords shown above are used, but do not share this format, they do not convey formal information in the RFC 2119 sense,
and are merely explanatory, i.e., informative. As much as possible, such usages are avoided in this specification.
</p>
<p>Normative sections provide requirements that authors, user agents and assistive technologies MUST follow for an implementation to conform to this specification.</p>
<p>
Non-normative (informative) sections provide information useful to understanding the specification. Such sections may contain examples of recommended practice, but it is not required to follow
such recommendations in order to conform to this specification.
</p>
</section>
<section id="mapping" class="normative">
<h2>Mapping <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> to Accessibility <abbr title="Application Programming Interfaces">APIs</abbr></h2>
<section id="mapping_general">
<h3>General rules for exposing <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> semantics</h3>
<p>This section <span class="rfc2119">MUST</span> conform to <a class="core-mapping" href="#mapping_general">General rules for exposing WAI-ARIA semantics</a> in [[!CORE-AAM-1.1]].</p>
</section>
</section>
<section id="mapping_conflicts" class="normative">
<h3>Conflicts between native markup semantics and <abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr></h3>
<p>User agents <span class="rfc2119">MUST</span> conform to <a class="core-mapping" href="#mapping_conflicts">Conflicts between native markup semantics and WAI-ARIA</a> in [[!CORE-AAM-1.1]].</p>
</section>
<section id="mapping_nodirect" class="normative">
<h3>Exposing attributes that do not directly map to accessibility <abbr title="application programming interface">API</abbr> properties</h3>
<p>
User agents <span class="rfc2119">MUST</span> conform to
<a class="core-mapping" href="#mapping_nodirect">Exposing attributes that do not directly map to accessibility <abbr title="application programming interface">API</abbr> properties</a> in
[[!CORE-AAM-1.1]].
</p>
</section>
<section id="mapping_role">
<h2>Role mapping</h2>
<p>
Platform <a class="termref">accessibility <abbr title="Application Programming Interfaces">APIs</abbr></a> traditionally have had a finite set of predefined <a class="termref">roles</a> that
are expected by <a class="termref">assistive technologies</a> on that platform and only one or two roles may be exposed. In contrast,
<abbr title="Accessible Rich Internet Application">WAI-ARIA</abbr> allows multiple roles to be specified as an ordered set of space-separated valid role tokens. The additional roles are
fallback roles similar to the concept of specifying multiple fonts in case the first choice font type is not supported.
</p>
<section id="roleMappingGeneralRules">
<h3>General Rules</h3>
<p>
User agents <span class="rfc2119">MUST</span> conform to the Role Mapping <a class="core-mapping" href="#roleMappingGeneralRules">General Rules</a> accessibility API computational
requirements in [[!CORE-AAM-1.1]].
</p>
</section>
<section id="mapping_role_table">
<h3>Role Mapping Table</h3>
<p>
This section defines how roles in graphics map to platform accessibility APIs based on their native host language semantics and when WAI-ARIA roles are applied. This section refers directly
to the Core Accessibility API Mappings specification.
</p>
<h4 id="role-map-graphics-document"><code>graphics-document</code></h4>
<table aria-labelledby="role-map-graphics-document">
<tbody>
<tr>
<th>Graphics-ARIA Specification</th>
<td>
<a class="graphics-role-reference" href="#graphics-document"><code>graphics-document</code></a>
</td>
</tr>
<tr>
<th><a href="https://w3c.github.io/core-aam/#roleMappingComputedRole">Computed Role</a></th>
<td>
<code>graphics-document</code>
</td>
</tr>
<tr>
<th>MSAA + IAccessible2 Role + Other IAccessible2 Features</th>
<td>
<p><code>ROLE_SYSTEM_DOCUMENT</code> + <code>STATE_SYSTEM_READONLY</code></p>
<p>IAccessible2: Object attribute <code>xml-roles:graphics-document</code>.</p>
</td>
</tr>
<tr>
<th><abbr title="User Interface Automation">UIA</abbr> Control Type + Other Features</th>
<td>Control Type: <code>'Document'</code>.</td>
</tr>
<tr>
<th><abbr title="Accessibility Toolkit">ATK</abbr>/<abbr title="Assistive Technology - Service Provider Interface">AT-SPI</abbr> Role</th>
<td>
<p>Expose <code>ROLE_DOCUMENT_FRAME</code> and object attribute <code>xml-roles:graphics-document</code>.</p>
</td>
</tr>
<tr>
<th><abbr title="Mac OS X Accessibility Protocol">AXAPI</abbr></th>
<td>
AXRole: <code>AXGroup</code><br />
AXSubrole: <code>AXDocument</code><br />
AXRoleDescription: <code>'document'</code>
</td>
</tr>
</tbody>
</table>
<h4 id="role-map-graphics-object"><code>graphics-object</code></h4>
<table aria-labelledby="role-map-graphics-object">
<tbody>
<tr>
<th>Graphics-ARIA Specification</th>
<td>
<a class="graphics-role-reference" href="#graphics-object"><code>graphics-object</code></a>
</td>
</tr>
<tr>
<th><a href="https://w3c.github.io/core-aam/#roleMappingComputedRole">Computed Role</a></th>
<td>
<code>graphics-object</code>
</td>
</tr>
<tr>
<th>MSAA + IAccessible2 Role + Other IAccessible2 Features</th>
<td>
<code>ROLE_SYSTEM_GROUPING</code> +
<p>IAccessible2: Object attribute <code>xml-roles:graphics-object</code>.</p>
</td>
</tr>
<tr>
<th><abbr title="User Interface Automation">UIA</abbr> Control Type + Other Features</th>
<td>Control Type: <code>'Group'</code>.</td>
</tr>
<tr>
<th><abbr title="Accessibility Toolkit">ATK</abbr>/<abbr title="Assistive Technology - Service Provider Interface">AT-SPI</abbr> Role</th>
<td>
<p>Expose <code>ROLE_PANEL</code> and object attribute <code>xml-roles:graphics-object</code>.</p>
</td>
</tr>
<tr>
<th><abbr title="Mac OS X Accessibility Protocol">AXAPI</abbr></th>
<td>
AXRole: <code>AXGroup</code><br />
AXSubrole: <code><nil></code><br />
AXRoleDescription: <code>'group'</code>
</td>
</tr>
</tbody>
</table>
<h4 id="role-map-graphics-symbol"><code>graphics-symbol</code></h4>
<table aria-labelledby="role-map-graphics-symbol">
<tbody>
<tr>
<th>Graphics-ARIA Specification</th>
<td>
<a class="graphics-role-reference" href="#graphics-symbol"><code>graphics-symbol</code></a>
</td>
</tr>
<tr>
<th><a href="https://w3c.github.io/core-aam/#roleMappingComputedRole">Computed Role</a></th>
<td>
<code>graphics-symbol</code>
</td>
</tr>
<tr>
<th>MSAA + IAccessible2 Role + Other IAccessible2 Features</th>
<td>
<code>ROLE_SYSTEM_GRAPHIC</code>
<p>IAccessible2: Object attribute <code>xml-roles:graphics-symbol</code>.</p>
</td>
</tr>
<tr>
<th><abbr title="User Interface Automation">UIA</abbr> Control Type + Other Features</th>
<td>Control Type: <code>'Image'</code>.</td>
</tr>
<tr>
<th><abbr title="Accessibility Toolkit">ATK</abbr>/<abbr title="Assistive Technology - Service Provider Interface">AT-SPI</abbr> Role</th>
<td>
<p>Expose <code>ROLE_IMAGE</code> and object attribute <code>xml-roles:graphics-symbol</code>.</p>
</td>
</tr>
<tr>
<th><abbr title="Mac OS X Accessibility Protocol">AXAPI</abbr></th>
<td>
AXRole: <code>AXImage</code><br />
AXSubrole: <code><nil></code><br />
AXRoleDescription: <code>'image'</code>
</td>
</tr>
</tbody>
</table>
</section>
</section>
<section class="appendix" id="changelog">
<h2>Change Log</h2>
<p>The full <a href="https://github.com/w3c/graphics-aam/commits/main/index.html">commit history to Graphics Accessibility API Mappings 1.0</a> is available.</p>
<!--<section>
<h2>Substantive changes since the <a href="@@">last public working draft</a></h2>
<ul>
<li>DD-MMM-YYYY: Change description.</li>
<!- EdNote: After each WD publish, move contents of this list into the next one below. ->
</ul>
</section>-->
<section>
<h2><!--Other s-->Substantive changes since the <a href="https://www.w3.org/TR/2016/WD-graphics-aam-1.0-20160908/">First Public Working Draft</a></h2>
<ul>
<li>2017-11-10: Fix macOS mapping for graphics-symbol.</li>
<li>2017-11-15: Fix ATK mappings</li>
<li>2017-12-04: Fix macOS mapping for graphics-symbol; Update UIA mappings</li>
<!-- EdNote: After each WD publish, move previous list into this one. -->
</ul>
</section>
</section>
<section class="appendix informative section" id="acknowledgements">
<h3>Acknowledgments</h3>
<p>The following people contributed to the development of this document.</p>
<ul id="gh-contributors"></ul>
<section class="section" id="ack_svga11y">
<h4>Participants active in the SVG accessibility task force at the time of publication</h4>
<ul>
<li>Amelia Bellamy-Royds (Invited expert)</li>
<li>Fred Esch (IBM Corporation)</li>
<li>Charles McCathieNevile (Yandex)</li>
<li>Charu Pandhi (IBM Corporation)</li>
<li>Doug Schepers (W3C Staff)</li>
<li>Richard Schwerdtfeger (Knowbility)</li>
<li>Léonie Watson (The Paciello Group)</li>
<li>Jason White (Educational Testing Service)</li>
</ul>
</section>
<section class="section" id="ack_group">
<h4>Participants active in the ARIA WG at the time of publication</h4>
<ul>
<li>David Bolter (Mozilla Foundation)</li>
<li>Michael Cooper (W3C/MIT)</li>
<li>James Craig (Apple Inc.)</li>
<li>Joanmarie Diggs (Igalia)</li>
<li>John Foliot (Invited Expert)</li>
<li>Christopher Gallelo (Microsoft Corporation)</li>
<li>Bryan Garaventa (SSB BART Group)</li>
<li>Jon Gunderson (University of Illinois at Urbana-Champaign)</li>
<li>Matthew King (IBM Corporation)</li>
<li>Dominic Mazzoni (Google, Inc.)</li>
<li>Shane McCarron (Invited Expert, Aptest)</li>
<li>James Nurthen (Oracle Corporation)</li>
<li>Janina Sajka (Invited Expert, The Linux Foundation)</li>
<li>Stefan Schnabel (SAP AG)</li>
<li>Lisa Seeman (Invited Expert)</li>
<li>Alexander Surkov (Mozilla Foundation)</li>
<li>Jason White (Educational Testing Service)</li>
</ul>
</section>
<div data-include="../common/acknowledgements/funders.html" data-include-replace="true"></div>
</section>
</body>
</html>