-
Notifications
You must be signed in to change notification settings - Fork 125
/
Copy pathindex.html
1248 lines (1196 loc) · 59.9 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
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
<!--?xml version='1.0' encoding='UTF-8'?-->
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US" xml:lang="en-US">
<head>
<meta charset="UTF-8" />
<title>WAI-ARIA Graphics Module</title>
<script src="https://www.w3.org/Tools/respec/respec-w3c-common" class="remove"></script>
<script src="common/script/resolveReferences.js" class="remove"></script>
<script src="common/biblio.js" class="remove"></script>
<link href="common/css/common.css" rel="stylesheet" type="text/css"/>
<script class="remove" src="common/script/ariaChild.js"></script>
<script class="remove" src="common/script/roleInfo.js"></script>
<script class="remove">
var respecConfig = {
trace: true,
doRDFa: '1.1',
includePermalinks: true,
permalinkEdge: true,
permalinkHide: false,
// 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",
diffTool: "http://www.aptest.com/standards/htmldiff/htmldiff.pl",
// the specifications short name, as in https://www.w3.org/TR/short-name/
shortName: "graphics-aria-1.0",
// if you wish the publication date to be other than today, set this
//publishDate: "2014-12-11",
copyrightStart: "2015",
// if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
// and its maturity status
previousPublishDate: "2015-12-03",
previousMaturity: "WD",
//prevRecURI: "https://www.w3.org/TR/2014/REC-wai-aria-20140320/",
//previousDiffURI: "https://www.w3.org/TR/2014/REC-wai-aria-20140320/",
// if there a publicly available Editors Draft, this is the link
edDraftURI: "https://w3c.github.io/graphics-aria/",
// 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: "[email protected]",
w3cid: 75809
},
{
name: "Joanmarie Diggs",
url: 'https://www.igalia.com',
mailto: "[email protected]",
company: "Igalia, S.L.",
companyURI: "https://www.igalia.com",
w3cid: 68182
},
{
name: "Michael Cooper",
url: 'http://www.w3.org',
mailto: "[email protected]",
company: "W3C",
companyURI: "http://www.w3.org",
w3cid: 34017
},
{
name: "Fred Esch",
mailto: "[email protected]",
company: "IBM Corporation",
companyURI: "http://www.ibm.com",
w3cid: 73593,
note: "until September 2016"
},
{
name: "Rich Schwerdtfeger",
mailto: "[email protected]",
company: "Knowbility",
companyURI: "https://www.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: "[email protected]",
w3cid: 75809
},
{
name: "Fred Esch",
mailto: "[email protected]",
company: "IBM Corporation",
companyURI: "http://www.ibm.com/",
w3cid: 73593
},
{
name: "Rich Schwerdtfeger",
mailto: "[email protected]",
company: "Knowbility",
companyURI: "https://www.knowbility.org/",
w3cid: 2460
},
{
name: "Doug Schepers",
mailto: "[email protected]",
company: "W3C",
companyURI: "https://www.w3.org/",
w3cid: 38635
}
],
/*
alternateFormats: [
{ uri: 'aria-diff.html', label: "Diff from Previous Recommendation" } ,
{ uri: 'aria.ps', label: "PostScript version" },
{ uri: 'aria.pdf', label: "PDF version" }
],
*/
// errata: 'https://www.w3.org/2010/02/rdfa/errata.html',
//processVersion: 2015,
// name of the WG
wg: ["Accessible Rich Internet Applications Working Group", "SVG Working Group"],
// URI of the public WG page
wgURI: ["https://www.w3.org/WAI/ARIA/", "https://www.w3.org/Graphics/SVG/WG/"],
// name (with the @w3c.org) of the public mailing to which comments are due
wgPublicList: "public-svg-a11y",
// URI of the patent status for this WG, for Rec-track documents
// !!!! IMPORTANT !!!!
// This is important for Rec-track documents, do not copy a patent URI from a random
// document unless you know what you're doing. If in doubt ask your friendly neighbourhood
// Team Contact.
wgPatentURI: ["https://www.w3.org/2004/01/pp-impl/83726/status", "https://www.w3.org/2004/01/pp-impl/19480/status"],
maxTocLevel: 4,
// Spec URLs
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/",
"REC": "https://www.w3.org/TR/wai-aria/"
},
localBiblio: biblio,
preProcess: [ linkCrossReferences ]
};
</script>
<style>
/* Styles for embedded object examples */
.example object, .example img {
display: block;
width: 35em;
max-width: 100%;
max-height: 100vh;
background-color: white;
border: solid 1px #999;
}
.example object[type="text/html"] {
height: 20em;
width: 60em;
}
</style>
</head>
<body>
<section id="abstract">
<p>Assistive technologies need semantic information about the structures and expected behaviors of a document in order to convey appropriate information to persons with disabilities. This specification defines a <a href="" class="specref">WAI-ARIA 1.1</a> [[!WAI-ARIA-1.1]] module of core <a data-lt="role">roles</a><!-- , <a data-lt="state">states</a> and <a data-lt="property">properties</a> Note, if we do include any states & properties in this module, edit this sentence! --> specific to web graphics. These semantics allow an author to express the logical structure of the graphic to assistive technologies. Assistive technologies could then enable semantic navigation and adapt styling and interactive features, to provide an optimal experience for the audience. These features complement the graphics and document structure elements defined by HTML [[HTML5]] and SVG [[SVG2]].</p>
<p>This document 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 Applications">WAI-ARIA</abbr> Overview</a>.</p>
</section>
<section id="sotd">
<p>This is an Editor's Draft of <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> Graphics Module 1.0 by the <a href="https://www.w3.org/WAI/PF/svg-a11y-tf/"><abbr title="Scalable Vector Graphics">SVG</abbr> Accessibility Taskforce</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>. </p>
<p>Feedback on any aspect of the specification is accepted. For this publication, the <abbr title="Scalable Vector Graphics">SVG</abbr> Accessibility Task Force particularly seeks feedback on the following questions:</p>
<ul>
<li>Are proposed roles clear and appropriate to the needs of interactive graphics?</li>
<li>Is the relationship of this specification to <a href="" class="specref">WAI-ARIA 1.1</a> clear?</li>
</ul>
<p>To comment, <a href="https://github.com/w3c/aria/issues/new">file an issue in the <abbr title="World Wide Web Consortium">W3C</abbr> ARIA GitHub repository</a>, using the "graphics" label in the issue. If this is not feasible, send email to <a href="mailto:[email protected]?subject=Graphics%20ARIA%20public%20comment">[email protected]</a> (<a href="https://lists.w3.org/Archives/Public/public-svg-a11y/">comment archive</a>). Comments are requested by <strong>30 September 2016</strong>. In-progress updates to the document may be viewed in the <a href="https://w3c.github.io/aria/aria/graphics.html">publicly visible editors' draft</a>.</p>
</section>
<section id="toc">
</section>
<section class="informative" id="introduction">
<h1>Introduction</h1>
<p><abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> is a technical specification that provides a framework to improve the accessibility and interoperability of web content and applications. It enables web browsers to map the accessibility semantics in web content to platform-specific accessibility APIs. This enables web content to be interoperable with platform assistive technologies, similar to native platform applications, without requiring authors to include platform dependencies.</p>
<p>This specification is a modular extension of <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> [[!WAI-ARIA-1.1]] designed to support graphics. The goals of this specification include:</p>
<ul>
<li>Expanding WAI-ARIA to produce semantic extensions to support structured graphics such as charts, graphs, maps, technical drawings and scientific diagrams. It has applicability to both Scalable Vector Graphics as well as HTML5 Canvas and graphics produced with CSS styling of HTML and other markup languages.</li>
<li>Align with a new governance model for modularization and extensions to <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr>.</li>
<li>Provide structural semantics extensions that will support both assistive technologies and enable semantic navigation, alternative styling, and interactivity support.</li>
<li>Work in harmony with SVG 2 and ARIA 1.1 to get consistent working accessibility infrastructure, on par with <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> and HTML 5.1, across all the major browsers.</li>
</ul>
<p>This specification defines the core roles that would be used in all structured graphics or diagrams.
It establishes the default roles that can be used to describe graphical markup elements such as shapes and canvases.
In combination with WAI-ARIA attributes to provide alternative text and to indicate relationships between elements, this provides a framework for annotating many figures and diagrams.
Future work will expand on this framework to enable more detailed annotation of data-rich graphics such as charts or maps.</p>
<p>For a more detailed explanation of <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> please refer to the <a href="https://www.w3.org/WAI/intro/aria">WAI-ARIA Introduction</a> and how it applies to Rich Internet Application Accessibility.</p>
<section id="target-audience">
<h2>Target Audience</h2>
<p>This specification defines a module of <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> for graphics, consisting of graphics-specific element <a data-lt="role">roles</a><!-- , <a data-lt="state">states</a>, <a data-lt="property">properties</a> and values Again, edit as required re states/properties -->. It impacts several audiences:</p>
<ul>
<li><a data-lt="user agent">User agents</a> that process content containing <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> and graphics <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> features;</li>
<li><a>Assistive technologies</a> that provide specialized reading experiences to users with disabilities;</li>
<li>Authors of web graphics;</li>
<li>Authoring tools that help authors create conforming graphics; and</li>
<li>Conformance checkers, that verify appropriate use of <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> and this <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> Graphics module.</li>
</ul>
<p>Each conformance requirement indicates the audience to which it applies.</p>
<!--p>Although this specification is applicable to the above audiences, it is not specifically targeted to, nor is it intended to be the sole source of information for, any of these audiences. In the future, additional documents will be created to assist authors in applying these <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> semantics for graphics and to define how the information in this document is mapped to platform accessibility APIs.</p-->
</section>
<section id="ua-support">
<h2>User Agent Support</h2>
<p>This module follows the general <a href="https://www.w3.org/TR/wai-aria-1.1/#ua-support">User Agent support principles</a> defined in WAI-ARIA [[!WAI-ARIA-1.1]].
The roles defined here do not require any change in behavior by user agents other than in the information exposed to the <a>accessibility API</a>.
However, the semantics defined here provide the ability for user agents to enhance the general user interface presented to readers.
For example, a user agent may provide alternative keyboard navigation suitable to a graphical environment, or may allow users to extract a copy of a graphic from a larger document.</p>
</section>
<section id="co-evolution">
<h2>Co-Evolution of <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> and Host Languages</h2>
<p>The <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> Graphics module follows the model for <a href="https://www.w3.org/TR/wai-aria-1.1/#co-evolution">co-evolution of <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> and host languages</a> defined in WAI-ARIA [[!WAI-ARIA-1.1]]. It is intended to augment semantics in supporting languages like HTML [[HTML5]], SVG [[SVG2]] and EPUB, or to be used as an accessibility enhancement technology in other markup-based languages that do not explicitly include support for ARIA.
WAI-ARIA <a>roles</a> clarify semantics to assistive technologies when authors create new types of objects, via style and script, or use markup languages which describe the visual appearance of a document rather than its meaning.</p>
<p>Although markup languages may provide some of these semantics natively, it is expected that there will be a persistent need for the semantics provided by the <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> Graphics module.
Some host languages exist to create semantics for features other than the user interface. For example, SVG expresses the semantics behind production of graphical objects, not of user interface components that those objects may represent. Host languages such as these might, by design, not provide native semantics that map to all of this specification's features. In these host languages, the <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> Graphics module could be adopted as a long-term approach to add semantic information.</p>
</section>
<section id="authoring_practices">
<h2>Authoring Practices</h2>
<section id="authoring_tools">
<h3>Authoring Tools</h3>
<p>Many of the requirements in the definitions of the <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> and Graphics <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> <a data-lt="role">roles</a>, <a data-lt="state">states</a> and <a data-lt="property">properties</a> can be checked automatically during the development process, similar to other quality control processes used for validating code. To assist authors who are creating graphics, these tools can compare the semantic structure of Graphics <abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr> roles from the <abbr title="Document Object Model">DOM</abbr> to that defined in this specification and notify the author of errors or simply create templates that enforce that structure.</p>
</section>
<section id="authoring_testing">
<h3>Testing Practices and Tools</h3>
<p>The accessibility of interactive content cannot be confirmed by static checks alone. Developers of interactive content should test for device-independent access to <a data-lt="widget">widgets</a> and applications, and should verify accessibility <abbr title="application programming interface">API</abbr> access to all content and changes during user interaction.</p>
</section>
</section>
<section id="at_support">
<h2>Assistive Technologies</h2>
<p>Programmatic access to accessibility semantics is essential for assistive technologies. For more information, refer to the <a href="https://www.w3.org/TR/wai-aria-1.1/#at_support">Assistive Technologies</a> section in WAI-ARIA [[!WAI-ARIA-1.1]].</p>
<p>For the graphics roles in particular, two categories of assistive technology are particularly relevant, but have different needs:</p>
<ul>
<li>Text-based presentations, such as screen readers, braille displays, and text-only displays or printers. These technologies need to replace a complex graphic with semantic text descriptions, preserving any meaningful structure and relationships between components.
</li>
<li>Alternative graphical presentations, such as colour-adjusted displays, screen magnifiers, large print documents, or embossing printers with graphic support. These technologies need to distinguish between graphical features which are primarily decorative and those which are essential for conveying the meaning of the content.</li>
</ul>
<p>The role descriptions suggest which features of an element with that role are considered semantically important and should be conveyed to the reader whenever possible.</p>
</section>
</section>
<section class="normative">
<h2>Conformance</h2>
<p>This specification indicates whether a section is <a class="termref">normative</a> or non-normative (<a class="termref">informative</a>) and the classification applies to the entire section. A statement "This section is normative" or "This section is non-normative" applies to all sub-sections of that section.</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 <strong class="rfc2119">MUST</strong>, <strong class="rfc2119">MUST NOT</strong>, <strong class="rfc2119">REQUIRED</strong>, <strong class="rfc2119">SHALL</strong>, <strong class="rfc2119">SHALL NOT</strong>, <strong class="rfc2119">SHOULD</strong>, <strong class="rfc2119">RECOMMENDED</strong>, <strong class="rfc2119">MAY</strong>, and <strong class="rfc2119">OPTIONAL</strong> 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 a <code>strong</code> 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>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 class="informative" id="terms">
<h1>Important Terms</h1>
<div data-include="common/terms.html" data-oninclude="restrictReferences"></div>
</section>
<section class="normative" id="roles">
<h1>Graphics Roles</h1>
<p>
This section defines additions to the
<abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr>
<a>role</a> <a>taxonomy</a>
and describes the characteristics and properties of all <a data-lt="role">roles</a>.
See <a href="#roles" class="specref">ARIA Roles</a> for descriptions
of the fields provided by this module.
</p>
<p>
Authors are given the ability to influence what is presented
to assistive technologies and to influence navigation through
the use of roles and properties.
This includes the ability to mark elements as having no semantic importance.
With graphics, there are many
cases where presenting and navigating every element will make the
graphic harder to understand and use.
</p>
<p>
Authors may mark elements for exclusion
from the semantic representation of the document
(the accessibility tree) by assigning
the role <rref>none</rref> or <rref>presentation</rref>.
The element with this role should be treated transparently
by assistive technologies, as if its children or text content
were directly contained by its parent element.
In addition, certain roles,
such as <rref>img</rref> or <rref>graphics-symbol</rref>,
when assigned to a parent element, will cause all child
DOM structure to be omitted from the accessibility tree.
This is indicated by the "Children Presentational"
value in the role characteristics table.
Finally, the native semantics of the graphics language
may also default to ignoring DOM structure that does not have
semantic data attached; for SVG, this is defined in the SVG Accessibility API Mappings specification [[SVG-AAM-1.0]].
</p>
<p>
In all cases, to be considered presentational, an element must not be interactive
and must not be assigned any accessible properties or alternative text.
A role of <code>none</code> or <code>presentation</code> will be ignored
for interactive elements or those with WAI-ARIA states and properties.</p>
<section id="role_definitions">
<h2>Definition of Roles</h2>
<p>
Below is an alphabetical list of the
<abbr title="Accessible Rich Internet Applications">WAI-ARIA</abbr>
<a data-lt="role">roles</a> defined in this specification.
They would normally be used in combination with other roles
defined in WAI-ARIA
to annotate graphics within documents and rich internet applications [[WAI-ARIA-1.1]].
</p>
<!-- -->
<p id="index_role">Placeholder for compact list of roles</p>
<div class="role">
<rdef>graphics-document</rdef>
<div class="role-description">
<p>
A type of <rref>document</rref> in which
the visual appearance or layout of content conveys meaning.
</p>
<p>
Similar to other <rref>document</rref> types,
the <code>graphics-document</code> role applies to the root element of
a region of the page containing related information,
where the user's primary interaction mode is expected to be
browsing the document rather than controlling an application.
The element with this role
may be the root element of the document file,
or of a nested structure within it.
</p>
<p>
The <code>graphics-document</code> may be distinguished
from similar roles as follows:
</p>
<ul>
<li><p>
Relative to other documents, a <code>graphics-document</code>
is distinguished by the semantic importance of its
visual (usually two-dimensional) representation.
User agents and assistive technologies
SHOULD take this into consideration
when supporting navigation of the graphic.
Accessibility technologies that re-format or re-style a document
SHOULD NOT alter the layout of a <code>graphics-document</code>
except in ways that are consistent
with the semantic roles and relationships of its content.
</p></li>
<li><p>
Relative to an <rref>img</rref>, a <code>graphics-document</code>
is distinguished by the structured nature of its content.
Its child elements may have semantic meaning,
and may include links or other interactive widgets.
</p></li>
<li><p>
Relative to a <rref>graphics-object</rref>,
a <code>graphics-document</code> is self-contained.
Its meaning persists when separated from surrounding content.
The element with the <code>graphics-document</code> role defines
the scope and context for interpretation of the child content.
</p></li>
</ul>
<p>
In general, authors SHOULD use the <code>graphics-document</code> role
for structured graphics such as
charts, maps, diagrams, technical drawing, blue prints and instructional graphics.
However, if a single large graphic has discrete regions
that may be safely re-arranged without sacrificing meaning,
each of those regions SHOULD be a distinct <code>graphics-document</code>.
An alternative role (such as <rref>figure</rref>)
may be used to group them together.
One <code>graphics-document</code> may also be nested inside another,
for example a bar chart that is embedded in a map
or a matrix of chart panels
should have a role of <code>graphics-document</code>.
The nested document provides encapsulation;
navigation between components of
the inner and outer graphics should be explicit.
</p>
<div class="note">
<p>
To support user agents and assistive technologies
based on the ARIA 1.0 specification,
authors may wish to include the <rref>document</rref> role
as a fallback value,
in the form <code>role="graphics-document document"</code>.
</p>
<p>
Future specifications may define more specific roles
for particular types of graphical documents with
special semantic structures. Those more specific roles
would be subclasses of <code>graphics-document</code>.
</p>
</div>
<pre class="example highlight">
<!-- An SVG diagram of an electrical circuit -->
<svg xmlns="https://www.w3.org/2000/svg"
width="400" height="200" viewBox="0 0 200 100"
role="graphics-document document" >
<title>A simple circuit</title>
<desc>A circuit with one source, one switch, and one load</desc>
<style type="text/css">
/* omitted */
</style>
<g id="battery-1" role="graphics-symbol img"
aria-roledescription="source"
aria-label="battery"
aria-flowto="switch-1"
transform="translate(20,50)" >
<path d="M-15,-5 h30 M-5,5 h10" />
</g>
<path class="wire" d="M20,45 V20 H90"/>
<g id="switch-1" role="graphics-symbol img"
aria-roledescription="switch"
aria-label="single-pole switch"
aria-flowto="lightbulb-1" >
<path d="M90,20 L105,30" />
<circle class="connection" cx="90" cy="20" r="2" />
<circle class="connection" cx="110" cy="20" r="2" />
</g>
<!-- more wires and a light bulb -->
</svg>
<object type="image/svg+xml" data="img/circuit-diagram.svg" ></object>
</pre>
</div>
<table class="role-features">
<caption>Characteristics:</caption>
<thead>
<tr>
<th scope="col">Characteristic</th>
<th scope="col">Value</th>
</tr>
</thead>
<tbody>
<tr>
<th class="role-abstract-head" scope="row">Is Abstract:</th>
<td class="role-abstract"> </td>
</tr>
<tr>
<th class="role-parent-head" scope="row">Superclass Role:</th>
<td class="role-parent"><rref>document</rref></td>
</tr>
<tr>
<th class="role-children-head" scope="row">Subclass Roles:</th>
<td class="role-children"> </td>
</tr>
<tr>
<th class="role-base-head" scope="row">Base Concept:</th>
<td class="role-base"> </td>
</tr>
<tr>
<th class="role-related-head" scope="row">Related Concepts:</th>
<td class="role-related">
<ul>
<li><rref>graphics-object</rref></li>
<li><rref>img</rref></li>
<li><rref>article</rref></li>
</ul>
</td>
</tr>
<tr>
<th class="role-scope-head" scope="row">Required Context Role:</th>
<td class="role-scope"> </td>
</tr>
<tr>
<th class="role-mustcontain-head" scope="row">Required Owned Elements:</th>
<td class="role-mustcontain"></td>
</tr>
<tr>
<th class="role-required-properties-head">Required States and Properties:</th>
<td class="role-required-properties"> </td>
</tr>
<tr>
<th class="role-properties-head" scope="row">Supported States and Properties:</th>
<td class="role-properties"> </td>
</tr>
<tr>
<th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
<td class="role-inherited"> </td>
</tr>
<tr>
<th class="role-namefrom-head" scope="row">Name From:</th>
<td class="role-namefrom">author</td>
</tr>
<tr>
<th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
<td class="role-namerequired">True</td>
</tr>
<tr>
<th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
<td class="role-namerequired-inherited"> </td>
</tr>
<tr>
<th class="role-childpresentational-head" scope="row">Children Presentational:</th>
<td class="role-childpresentational">False</td>
</tr>
<tr>
<th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
<td class="role-presentational-inherited"> </td>
</tr>
<tr>
<th class="implicit-values-head">Implicit Value for Role:</th>
<td class="implicit-values"> </td>
</tr>
</tbody>
</table>
</div>
<div class="role">
<rdef>graphics-object</rdef>
<div class="role-description">
<p>
A section of a <rref>graphics-document</rref>
that represents a distinct object or sub-component
with semantic meaning.
A graphical object may itself have nested sub-components.
</p>
<p>
Container elements that instead represent a collection
of disconnected objects should instead be given the
<rref>group</rref> or <rref>list</rref> roles.
Grouping elements that do not have semantic meaning
and do not alter the semantic context provided by an ancestor
SHOULD NOT be given a role,
which may be explicitly indicated
with the role <rref>none</rref> or <rref>presentation</rref>.
</p>
<p>
Unlike a <rref>graphics-document</rref>,
a <code>graphics-object</code> need not be self-contained,
and it does not establish a new context for navigation.
However, user agents and assistive technologies
SHOULD provide a way for users, particularly non-visual users,
to navigate the nested structure of objects
in a hierarchical manner, similar to nested lists.
</p>
<p class="note">
To support user agents and assistive technologies
based on the ARIA 1.0 specification,
authors may wish to include the <rref>group</rref> role
as a fallback value,
in the form <code>role="graphics-object group"</code>.
</p>
<div class="example">
<p>
The code that follows is a portion of the markup for a
structured graphic. It includes SVG <code>g</code> grouping
elements with various roles:
</p>
<ul>
<li>
<code>graphics-object</code> for distinct objects,
such as the house, its door, or roof.</li>
<li>
<rref>group</rref> to group together the windows
or the trees (multiple distinct objects)
with a single label or description.
</li>
<li>
<rref>img</rref> for the background which is described as a whole.
</li>
<li>
<rref>none</rref> for elements that apply styles or transformations
without having any semantic meaning.
</li>
</ul>
<p>
Where a graphical object has multiple sub-components, the
group role is provided as an explicit fallback.
</p>
<object type="image/svg+xml" data="img/house-graphicsroles.svg"></object>
<pre class="highlight">
<svg xmlns="https://www.w3.org/2000/svg"
width="600" height="400" viewBox="0 0 600 400"
role="graphics-document document" xml:lang="en">
<title>Home</title>
<g role="img" aria-label="background">
<desc>Blue sky, sunshine, and green grass</desc>
<!-- The multiple parts of the background form a single image
conveyed by that one description. -->
<rect fill="lightSkyBlue" height="100%" width="100%" />
<circle fill="yellow" stroke="gold" stroke-width="4"
cx="0" cy="0" r="50" />
<path fill="none" stroke="gold" stroke-width="3"
d="..." />
<rect fill="#6a2" y="300" width="100%" height="100" />
</g>
<g role="graphics-object group"
aria-labelledby="house-label"
transform="translate(100,325)">
<desc>A two-storey brick house, drawn with basic shapes.
</desc>
<!-- The house has a number of details worth calling out,
so it is a graphical object -->
<rect fill="firebrick" stroke="darkRed"
width="300" height="200" y="-200"
role="none" /><!-- the walls of the house are
already described thoroughly,
so no role is required -->
<g role="graphics-object" aria-label="door"
transform="translate(30,-90)">
<desc>The brown door on the left side of the building
has a window and a round doorknob</desc>
<!-- The graphical object role allows for further
nested sub-components.
However, based on the default SVG API mappings,
these shapes, which have neither labels nor descriptions,
will be treated as presentation. -->
<rect fill="darkKhaki" stroke="#632"
width="50" height="90"/>
<rect fill="lightSteelBlue" stroke="#632" stroke-width="4"
x="5" y="5" width="40" height="30" />
<circle fill="gray" stroke="#444" stroke-width="0.7"
cx="10" cy="50" r="4" />
</g>
<g role="group" aria-label="windows"
fill="lightSteelBlue" stroke="#632" stroke-width="6">
<!-- The windows are distinct objects,
grouped together with a common label -->
<g role="none" transform="translate(0,-85)">
<rect aria-label="first-floor window"
x="100" width="25" height="45">
<desc>A small window beside the door</desc>
</rect>
<path aria-label="first-floor living-room window"
d="M180,0h100v60h-100v-60z
m30,0v60 m40,0v-60">
<desc>A large three-pane window fills
the rest of the first floor</desc>
</path>
</g>
<g role="none" transform="translate(0,-180)">
<!-- more windows on the second floor -->
</g>
</g>
<!-- more markup for the roof and chimney -->
<text id="house-label"
font-family="cursive" font-size="36px"
x="70" y="50">My House</text>
</g>
<!-- more markup for the trees -->
</svg>
</pre>
</div>
<!--
FRED: I've added more explanation to the house example,
which I think covers the factors you were trying to emphasize here.
OK to omit the second example?
<div class="example">
<p>
In the example below, the outer most group element has the role <code>graphics-object</code>. The outer group represents
the set of labels for the months of the year. The inner group elements exist for style purposes, do not have semantic
meaning and thus are given the role none.
</p>
<pre class="highlight">
<g role='graphics-object' >
<text x="376.01" y="248.66" >Jan</text>
<text x="325.32" y="336.46" >Feb</text>
<g role='none'>
<text x="237.52" y="387.15" >Mar</text>
<g text-anchor="end" role='none'>
<text x="136.14" y="387.15" >Apr</text>
<text x="48.34" y="336.46" >May</text>
</g>
</g>
<g text-anchor="end" role='none'>
<text x="-2.346" y="248.66" >Jun</text>
<text x="-2.346" y="147.28" >Jul</text>
<g role='none'>
<text x="48.34" y="59.48" >Aug</text>
<text x="136.14" y="8.794" >Sep</text>
</g>
</g>
<g text-anchor="start" role='none'>
<text x="237.52" y="8.794" >Oct</text>
<text x="325.32" y="59.48" >Nov</text>
<text x="376.01" y="147.28" >Dec</text>
</g>
</g>
</pre>
<object type="image/svg+xml" data="img/monthsCircle.svg"></object>
</div>
-->
</div>
<table class="role-features">
<caption>Characteristics:</caption>
<thead>
<tr>
<th scope="col">Characteristic</th>
<th scope="col">Value</th>
</tr>
</thead>
<tbody>
<tr>
<th class="role-abstract-head" scope="row">Is Abstract:</th>
<td class="role-abstract"> </td>
</tr>
<tr>
<th class="role-parent-head" scope="row">Superclass Role:</th>
<td class="role-parent"><rref>group</rref></td>
</tr>
<tr>
<th class="role-children-head" scope="row">Subclass Roles:</th>
<td class="role-children"> </td>
</tr>
<tr>
<th class="role-base-head" scope="row">Base Concept:</th>
<td class="role-base"> </td>
</tr>
<tr>
<th class="role-related-head" scope="row">Related Concepts:</th>
<td class="role-related">
<ul>
<li><rref>graphics-document</rref></li>
<li><rref>group</rref></li>
<li><rref>img</rref></li>
<li><rref>graphics-symbol</rref></li>
</ul>
</td>
</tr>
<tr>
<th class="role-scope-head" scope="row">Required Context Role:</th>
<td class="role-scope"> </td>
</tr>
<tr>
<th class="role-mustcontain-head" scope="row">Required Owned Elements:</th>
<td class="role-mustcontain"></td>
</tr>
<tr>
<th class="role-required-properties-head">Required States and Properties:</th>
<td class="role-required-properties"> </td>
</tr>
<tr>
<th class="role-properties-head" scope="row">Supported States and Properties:</th>
<td class="role-properties"> </td>
</tr>
<tr>
<th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
<td class="role-inherited"> </td>
</tr>
<tr>
<th class="role-namefrom-head" scope="row">Name From:</th>
<td class="role-namefrom">
<ul>
<li>author</li>
<li>contents</li>
</ul>
</td>
</tr>
<tr>
<th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
<td class="role-namerequired">False</td>
</tr>
<tr>
<th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
<td class="role-namerequired-inherited"> </td>
</tr>
<tr>
<th class="role-childpresentational-head" scope="row">Children Presentational:</th>
<td class="role-childpresentational">False</td>
</tr>
<tr>
<th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
<td class="role-presentational-inherited"> </td>
</tr>
<tr>
<th class="implicit-values-head">Implicit Value for Role:</th>
<td class="implicit-values"> </td>
</tr>
</tbody>
</table>
</div>
<div class="role">
<rdef>graphics-symbol</rdef>
<div class="role-description">
<p>
A graphical object used to convey a simple meaning or category,
where the meaning is more important
than the particular visual appearance.
It may be a component of a larger structured graphic
such as a chart or map.
The symbol itself is an atomic object;
children are presentational.
</p>
<p>
When used as part of a structured symbolic language,
the <pref>aria-roledescription</pref> property
(introduced in ARIA 1.1 [[WAI-ARIA-1.1]])
can be used to name the symbol type
separately from the name and description
for the particular instance of the symbol.
</p>
<p class="note">
To support user agents and assistive technologies
based on the ARIA 1.0 specification,
authors may wish to include the <rref>img</rref> role
as a fallback value,
in the form <code>role="graphics-symbol img"</code>,
if that is not already the default semantic role for the element.
</p>
<pre class="example highlight">
<!-- Within an HTML document listing a restaurant menu -->
<h2>Appetizers</h2>
<ul>
<li> Spinach Salad with Strawberry & Almonds
<img role="graphics-symbol" title="Vegetarian" src="../assets/leaf.svg" />
<img role="graphics-symbol" title="Contains Nuts" src="../assets/peanut.svg" />
</li>
<li> Chicken Satay with Peanut Sauce
<img role="graphics-symbol" title="Contains Nuts" src="../assets/peanut.svg" />
</li>
<!-- … -->
</ul>
</pre>
<pre class="example highlight">
<!-- Within an SVG diagram of an electrical circuit -->
<g id="lightbulb-1" role="graphics-symbol img"
aria-roledescription="load"
aria-label="lightbulb"
aria-describedby="lightbulb-1-label"
aria-flowto="battery-1"
transform="translate(180,50)">
<text id="lightbulb-1-label"
x="-15" dy="0.5ex" text-anchor="end" >10W</text>
<circle r="10" />
<path d="M0,-10 C0,8 5,8 5,0 C5,-8 0,-8 0,10" />
</g>
<object type="image/svg+xml" data="img/circuit-diagram.svg" ></object>
</pre>
<pre class="example highlight">
<!-- Within an architectural blueprint-style SVG diagram -->
<g role="graphics-symbol img">
<title>Door</title>
<desc>on West side of South wall</desc>
<line stroke-width="8" stroke="white"
x1="50" y1="275" x2="150" y2="275"/>
<line stroke-width="4" stroke="#444"
x1="50" y1="275" x2="125" y2="225"/>
</g>
<!-- … -->
<use xlink:href="#outlet" role="graphics-symbol img"
x="5" y="130" width="40" height="40">
<title>Electrical outlet</title>
<desc>at center of West wall</desc>
</use>
<object type="image/svg+xml" data="img/blueprint.svg" ></object>
</pre>
</div>
<table class="role-features">
<caption>Characteristics:</caption>
<thead>
<tr>
<th scope="col">Characteristic</th>
<th scope="col">Value</th>
</tr>
</thead>
<tbody>
<tr>
<th class="role-abstract-head" scope="row">Is Abstract:</th>
<td class="role-abstract"> </td>
</tr>
<tr>
<th class="role-parent-head" scope="row">Superclass Role:</th>
<td class="role-parent"><rref>img</rref></td>
</tr>
<tr>
<th class="role-children-head" scope="row">Subclass Roles:</th>
<td class="role-children"> </td>
</tr>
<tr>
<th class="role-base-head" scope="row">Base Concept:</th>
<td class="role-base"> </td>
</tr>
<tr>
<th class="role-related-head" scope="row">Related Concepts:</th>
<td class="role-related"><a href="https://en.wikipedia.org/wiki/Symbol">symbol</a></td>
</tr>
<tr>
<th class="role-scope-head" scope="row">Required Context Role:</th>
<td class="role-scope"> </td>
</tr>
<tr>
<th class="role-mustcontain-head" scope="row">Required Owned Elements:</th>
<td class="role-mustcontain"></td>
</tr>
<tr>
<th class="role-required-properties-head">Required States and Properties:</th>
<td class="role-required-properties"> </td>
</tr>
<tr>
<th class="role-properties-head" scope="row">Supported States and Properties:</th>
<td class="role-properties"> </td>
</tr>
<tr>
<th class="role-inherited-head" scope="row">Inherited States and Properties:</th>
<td class="role-inherited"> </td>
</tr>
<tr>
<th class="role-namefrom-head" scope="row">Name From:</th>
<td class="role-namefrom">author</td>
</tr>
<tr>
<th class="role-namerequired-head" scope="row">Accessible Name Required:</th>
<td class="role-namerequired">True</td>
</tr>
<tr>
<th class="role-namerequired-inherited-head" scope="row">Inherits Name Required:</th>
<td class="role-namerequired-inherited"> </td>
</tr>
<tr>
<th class="role-childpresentational-head" scope="row">Children Presentational:</th>
<td class="role-childpresentational">True</td>
</tr>
<tr>
<th class="role-presentational-inherited-head" scope="row">Inherits Presentational:</th>
<td class="role-presentational-inherited"> </td>
</tr>
<tr>
<th class="implicit-values-head">Implicit Value for Role:</th>
<td class="implicit-values"> </td>
</tr>
</tbody>
</table>
</div>
</section>
<section id="role_other">
<h2>Other Roles for Graphics</h2>
<p> The following core ARIA roles, defined in ARIA 1.1 [[WAI-ARIA-1.1]], are also
relevant for annotating graphics:
</p>
<ul>
<li>
<rref>img</rref> (image) defines a single graphic
that is perceived as an indivisible whole.
Unlike a <rref>graphics-document</rref>,
an image cannot have navigable or interactive child content.
Unlike a <rref>graphics-symbol</rref>,
an image may require a detailed text description
to fully convey its meaning to non-visual users.
</li>
<li>
<rref>figure</rref> defines a container element
for content (including graphics) that is a key part
of the containing document but is outside the
normal reading stream.
A figure will often contain one or more elements
with the <rref>img</rref> or <rref>graphics-document</rref> roles,
but may also contain text captions, credits, or other related content.
</li>
</ul>
<p>
The following examples demonstrate appropriate use of
<rref>img</rref>, <rref>figure</rref>, and <rref>graphics-document</rref>
in a document.
</p>
<div class="example">
<p>
Within an HTML 5 document, an inline SVG
may sometimes represent an atomic <code>img</code>.
If the graphics form part of the natural reading flow
of the text, then this role is sufficient, as in the first example:
</p>