This repository has been archived by the owner on Sep 13, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 10
/
index.html
968 lines (885 loc) · 62.5 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
<!DOCTYPE html>
<html>
<head>
<title>Digital Publishing and Accessibility in W3C Documents</title>
<meta charset='utf-8'>
<script src="https://www.w3.org/Tools/respec/respec-w3c-common" async="" class="remove"></script>
<script class='remove'>
var respecConfig = {
localBiblio: {
"EPUB3": {
"authors": [
"Garth Conboy",
"Matt Garrish",
"Markus Gylling",
"William McCoy",
"Murata Makoto",
"Daniel Weck"
],
"title": "EPUB 3 Overview",
"href" : "http://www.idpf.org/epub/301/spec/epub-overview-20140626.html",
"rawDate": "26 June 2014",
"status" : "Recommended Specification",
"publisher": "IDPF"
},
"EPUB3.1": {
"authors": [
"Garth Conboy",
"Matt Garrish",
"Markus Gylling",
"William McCoy",
"Murata Makoto",
"Daniel Weck"
],
"title": "EPUB 3.1 Work Plan",
"href" : "http://www.idpf.org/workplans/2015/epub/",
"rawDate": "2016",
"status" : "Working Editor Draft Specification",
"publisher": "IDPF"
},
"CSS-Paged-Media": {
"authors": [
"Melinda Grant",
"Elika J. Etemad",
"Håkon Wium Lie",
"Simon Sapin"
],
"title": "Page-Margin Boxes",
"href": "http://www.w3.org/TR/css3-page/#margin-boxes",
"rawDate": "14 March 2013",
"publisher": "W3C"
},
"CSS3-Selector-First-Letter": {
"authors": [
"Tantek Çelik",
"Elika J. Etemad",
"Daniel Glazman",
"Ian Hickson",
"Peter Linss",
"John Williams"
],
"title": "Selectors Level 3",
"href": "http://www.w3.org/TR/css3-selectors/#first-letter",
"rawDate": "11 September 2011",
"publisher": "W3C"
},
"IDPF-GITHUB": {
"authors": [
"Matt Garrish",
"Nachiket Patel",
"Peter Krautzberger",
"Romain Deltour",
"Ron Severdia",
"Tobias Fischer"
],
"title": "IDPF's Github repository",
"href" : "https://github.com/IDPF",
"publisher": "IDPF"
},
"IDPF": {
"title": "International Digital Publishing Forum",
"href" : "http://idpf.org/",
"publisher": "IDPF"
},
"IDPF-Guide-Logical-Reading-Order": {
"title": "EPUB 3 Accessibility Guidelines: Logical Reading Order",
"href" : "http://www.idpf.org/accessibility/guidelines/content/semantics/order.php",
"publisher": "IDPF"
},
"IDPF-EPUB-Structure-Semantics-Vocabulary": {
"title": "EPUB 3 Structural Semantics Vocabulary",
"href" : "http://www.idpf.org/epub/vocab/structure/",
"rawDate": "30 January 2016",
"publisher": "IDPF"
},
"IDPF-CONTACT": {
"title": "IDPF Contact Page",
"href" : "http://idpf.org/contact-us",
"rawDate": "2016",
"publisher": "IDPF"
},
"IMS-Global": {
"title": "IMS Global Learning Consortium: Contact Us",
"href" : "https://www.imsglobal.org/contactus.cfm",
"publisher": "IMS Global Learning Consortium"
},
"IMS-Global-QTI": {
"title": "IMS Question & Test Interoperability® Specification",
"href" : "https://www.imsglobal.org/question/index.html",
"publisher": "IMS Global Learning Consortium"
},
"IMS-Global-APIP": {
"title": "Accessible Portable Item Protocol® (APIP®)",
"href" : "https://www.imsglobal.org/apip/index.html",
"publisher": "IMS Global Learning Consortium"
},
"PDF-Techniques-for-WCAG-2.0": {
"title": "PDF Techniques for WCAG 2.0",
"href" : "https://www.w3.org/TR/2014/NOTE-WCAG20-TECHS-20140408/pdf.html",
"publisher": "W3C"
},
"SCHEMA-ORG": {
"title": "Schema.org",
"href" : "https://schema.org/",
"publisher": "Schema.org"
},
"WEB-SCHEMAS": {
"title": "WebSchemas Accessibility wiki page",
"href" : "https://www.w3.org/wiki/WebSchemas/Accessibility",
"publisher": "W3C"
},
"ONIX-EPUBLICATION": {
"title": "ONIX E-publication Accessibility Details (List 196)",
"href" : "http://www.editeur.org/files/ONIX%20for%20books%20-%20code%20lists/ONIX_BookProduct_Codelists_Issue_32.html#codelist196",
"publisher": "Editeur"
},
"PDF-UA": {
"title": "PDF/UA",
"href" : "https://en.wikipedia.org/wiki/PDF/UA",
"publisher": "WIKIPEDIA"
},
"BENETECH": {
"title": "Benetech",
"href" : "https://www.benetech.org/",
"publisher": "Benetech"
},
"ETS": {
"title": "Educational Testing Service",
"href" : "https://www.ets.org/contact",
"publisher": "Educational Testing Service"
},
"ACCESSIBLE-ONLINE-LEARNING": {
"title": "Accessible Online Learning Community Group",
"href" : "https://www.w3.org/community/accesslearn/",
"publisher": "W3C"
},
"DAISY": {
"authors": [
"DAISY Consortium"
],
"title": "Daisy 2.02 Skippable Structures Recommendation",
"href": "http://www.daisy.org/z3986/specifications/d202skiprec/d202_skippability_rec.html",
"rawDate": "06 June 2003",
"publisher": "DAISY Consortium"
},
"DAISY-DTD": {
"authors": [
"DAISY Consortium"
],
"title": "DAISY Digital Talking Book [Z3986-2005]",
"href": "http://www.daisy.org/daisyniso-standard-dtd-and-css-files",
"rawDate": "2005",
"publisher": "DAISY Consortium"
},
"ANSI-NISO-Z39.98-2012": {
"authors": [
"DAISY Consortium"
],
"title": "Authoring and Interchange Framework for Adaptive XML Publishing Specification",
"href": "http://www.daisy.org/z3998/2012/z3998-2012.html",
"rawDate": "2012",
"publisher": "DAISY Consortium"
},
"ARIA-WG":{
"authors": [
"Accessible Rich Internet Applications (WAI-ARIA) WG"
],
"title": "Accessible Rich Internet Applications (WAI-ARIA)",
"href": "https://github.com/w3c/aria",
"publisher": "W3C"
},
"DPub-IG":{
"authors": [
"Digital Publishing Interest Group"
],
"title": "Digital Publishing Interest Group",
"href": "https://www.w3.org/dpub/IG/wiki/Main_Page",
"publisher": "W3C"
},
"DPub-ARIA-FootNote":{
"authors": [
"Digital Publishing Interest Group"
],
"title": "Digital Publishing Interest Group discussion about nested headings",
"href": "http://www.w3.org/TR/2015/WD-dpub-aria-1.0-20150707/#dpub-footnote",
"rawDate": "07 July 2015",
"publisher": "W3C"
},
"DPub-ARIA-FootNotes":{
"authors": [
"Digital Publishing Interest Group"
],
"title": "Digital Publishing Interest Group discussion about nested headings",
"href": "http://www.w3.org/TR/2015/WD-dpub-aria-1.0-20150707/#dpub-footnotes",
"rawDate": "07 July 2015",
"publisher": "W3C"
},
"DPub-Minutes-3":{
"authors": [
"Digital Publishing Interest Group"
],
"title": "Digital Publishing Interest Group discussion about nested headings",
"href": "http://www.w3.org/2015/05/15-dpub-minutes.html#item03",
"rawDate": "15 May 2015",
"publisher": "W3C"
},
"DPub-Minutes-4":{
"authors": [
"Digital Publishing Interest Group"
],
"title": "Digital Publishing Interest Group discussion about list titles",
"href": "http://www.w3.org/2015/05/15-dpub-minutes.html#item04",
"rawDate": "15 May 2015",
"publisher": "W3C"
},
"DPub-Accessibility-Wiki":{
"authors": [
"Digital Publishing Accessibility Task Force"
],
"title": "A11Y DPub Techniques based on WCAG 2.0",
"href": "https://github.com/w3c/dpub-accessibility/wiki/A11Y-DPub-Techniques-based-on-WCAG",
"rawDate": "2016",
"publisher": "DPub W3C"
},
"DIAGRAM-Center":{
"authors": [
"DIAGRAM Center"
],
"title": "Digital Image and Graphic Resources for Accessible Materials",
"href": "http://diagramcenter.org/",
"rawDate": "2016",
"publisher": "DIAGRAM Center"
},
"DIAGRAMMAR":{
"authors": [
"DIAGRAM Center"
],
"title": "Diagrammar: A Framework for Making Images and Graphics Accessible",
"href": "http://diagramcenter.org/standards-and-practices/content-model.html",
"rawDate": "2016",
"publisher": "DIAGRAM Center"
},
"READIUM":{
"authors": [
"Readium Foundation"
],
"title": "Readium Foundation",
"href": "http://readium.org/participate/contributing",
"publisher": "Readium Foundation"
},
"ANNOTATIONS-WG":{
"authors": [
"Annotations Working Group"
],
"title": "Web Annotation Working Group",
"href": "https://www.w3.org/annotation/",
"publisher": "W3C"
},
"WAI-IG-Minutes":{
"authors": [
"WAI Interest Group"
],
"title": "Discussion about deaply nested headings",
"href": "https://lists.w3.org/Archives/Public/w3c-wai-ig/2015AprJun/0039.html",
"rawDate": "23 April 2015",
"publisher": "W3C"
},
"WAI-Wiki": {
"authors": [
"WAI Members"
],
"title": "Using role=“heading” to identify headings",
"href": "https://www.w3.org/WAI/GL/wiki/Using_role%3Dheading",
"rawDate": "12 September 2013"
},
"SOWETO": {
"authors": [
"Kamau Brathwaite"
],
"title": "Soweto",
"href" : "http://www.poetryfoundation.org/poem/177297",
"rawDate": "1993",
"publisher": "Kamau Brathwaite"
},
"WOMEN": {
"authors": [
"May Swenson"
],
"title": "Women",
"href" : "http://www.poetryfoundation.org/poem/178001",
"rawDate": "1978",
"publisher": "May Swenson"
},
"MOUSE": {
"authors": [
"Lewis Carroll"
],
"title": "The Mouse's Tail",
"href" : "http://bootless.net/mouse.html",
"rawDate": "1865",
"publisher": "Lewis Carroll"
},
"HEADSHOTS": {
"authors": [
"Ceres Lee"
],
"title": "Headshots",
"href" : "http://web.mit.edu/puzzle/www/2015/puzzle/headshots/",
"rawDate": "2015",
"publisher": "Ceres Lee"
},
"Math-on-Webpages-CG": {
"authors": [
"W3C"
],
"title": "Getting Math Onto Web Pages Community Group",
"href" : "https://www.w3.org/community/mathonwebpages/"
},
"MATHJAX": {
"authors": [
"MathJax Consortium"
],
"title": "MathJax",
"href" : "https://www.mathjax.org"
},
"MATHQUILL": {
"authors": [
"Han Seoul-Oh",
"Jeanine Adkisson",
"Mary Stufflebeam"
],
"title": "MathQuill",
"href" : "http://mathquill.com/"
},
"MATHEMATICAL": {
"authors": [
"Garen Torikian"
],
"title": "mathematical",
"href" : "https://github.com/gjtorikian/mathematical"
},
"PROGRESSIVE": {
"authors": [
"Volker Sorge"
],
"title": "ProgressiveAccess",
"href" : "http://www.progressiveaccess.com/chemistry/index.php"
},
"AVOGADRO": {
"authors": [
"Marcus D Hanwell",
"Donald E Curtis",
"David C Lonie",
"Tim Vandermeersch",
"Eva Zurek",
"Geoffrey R Hutchison"
],
"title": "Avogadro",
"href" : "http://avogadro.cc/wiki/Main_Page"
},
"JCHEMPAINT": {
"authors": [
"Ralf Stephan",
"John May"
],
"title": "JChemPaint",
"href" : "http://jchempaint.github.io/"
}
},
specStatus: "IG-NOTE",
publishDate: "2016-05-03",
shortName: "dpub-accessibility",
editors: [
{
name: "Deborah Kaplan",
url: "http://suberic.net/~deborah.kaplan/",
company: "Invited Expert, Safari Books Online",
companyURL: "https://www.safaribooksonline.com/",
mailto: "[email protected]"
},
{
name: "Charles LaPierre",
url: "",
company: "Benetech",
companyURL: "https://www.benetech.org/",
mailto: "[email protected]"
}
],
previousMaturity: "",
previousPublishDate: "",
previousURI: "",
edDraftURI: "http://w3c.github.io/dpub-accessibility/",
wg: "Digital Publishing Interest Group",
wgURI: "http://www.w3.org/dpub/IG/",
wgPublicList: "public-digipub",
noRecTrack: "true",
otherLinks: [
{
key: "Repository",
data: [{
value: "Github Repository",
href: "https://github.com/w3c/dpub-accessibility"
}]
},
{
key: "Issues tracker",
data: [{
value: "Github Issue Tracker",
href: "https://github.com/w3c/dpub-accessibility/issues"
}]
},
],
alternateFormats: [
{
uri: "dpub-accessibility.epub",
label: "ePub"
}
],
charterDisclosureURI : "http://www.w3.org/2004/01/pp-impl/64149/status",
copyrightStart : 2014,
// 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: "http://www.w3.org/2004/01/pp-impl/64149/status",
// !!!! IMPORTANT !!!! MAKE THE ABOVE BLINK IN YOUR HEAD
};
</script>
<style type="text/css">
.source { text-align: right; font-style: normal;}
blockquote p { font-style: italic; }
/* --- status --- */
div.status-title {
min-width: 7.5em;
color: #b9ab2d;
}
div.status-title span {
text-transform: uppercase;
}
aside.status, div.status, div.illegal-status {
padding: 0.5em;
margin: 1em 0;
position: relative;
clear: both;
}
div.illegal-status { color: red }
div.illegal-status p { color: black }
aside.status, div.status {
padding: .5em;
border-left-width: .5em;
border-left-style: solid;
border-color: #00008B;
background: #fcfaee;
}
aside.status div.status {
border-left-width: .1em;
border-color: #999;
background: #fff;
}
aside.status div.status div.status-title {
color: #999;
}
div.status:before {
content: 'Can CSS Do This?';
text-transform: uppercase;
font-family: sans-serif;
color: #00008B;
}
</style>
</head>
<body>
<section id='abstract'>
<p>
This document describes how W3C guidelines (including but not limited to [[WCAG20]], [[ATAG20]], [[UAAG20]], and [[WAI-ARIA]]) and their principles, guidelines, and success criteria can be applied to the needs of Digital Publishing. It provides informative guidance, but does not set requirements.</p>
</section>
<section id='sotd'>
<p>
<strong>This is a work in progress. No section should be considered final, and the absence of any content does not imply that such content is out of scope, or may not appear in the future.</strong>
</p>
</section>
<section class="introductory">
<h2 id="intro">Introduction</h2>
<p>This document provides a gap analysis concerning Digital Publishing needs in the context of existing WAI W3C guidelines including (but not limited to) [[WCAG20]], [[ATAG20]], [[UAAG20]], and [[WAI-ARIA]]. Where appropriate, this document is also informed by other ongoing W3C projects including, but not limited to, Portable Web Publications [PWP] and the Web Annotation Working Group.</p>
<p>The World Wide Web Consortium (W3C)'s W3C Web Accessibility Initiative (WAI) is primarily concerned with web technologies; however, its guidance is also relevant to technologies which are not exclusively web technologies. The digital publishing industry, which creates composite web and non-web publications using web-based technology tools and standards, is reliant on the standards set by the W3C.</p>
<p>The current document is focused on the accessibility of digital publishing to people with disabilities and is not intended to supplant any other W3C work. </p>
</section>
<section class="introductory">
<h3>The W3C and Digital Publishing</h3>
<p><em>Digital Publishing</em> is a generic term for the broad ecosystem of electronic journals, magazines, news, or book publishing (authors, creators, publishers, news organizations, booksellers, accessibility and internationalization specialists, etc.). Formats used by eBook readers and tablets for electronic books, magazines, journals, and educational resources are W3C Technology-based. (X)HTML, CSS, SVG, SMIL, MathML, and various Web APIs are all part of modern digital publishing workflows. Commercial publishers also rely on W3C technologies in their back-end production workflows all the way from authoring through to delivering printed or electronic product and beyond. In general, one can say that the Publishing Industry is one of the largest communities relying heavily on W3C specifications and technologies.</p>
<p> However, a gap currently exists between the alignment of Publishing Industry needs and the various W3C recommendations. Features necessary for the success of digital publishing may be missing in W3C documents, or may be in draft only; as a result, for example, EPUB 3, the standard for electronic books, introduced extensions to support publishing-specific requirements.</p>
</section>
<!--
<section class="introductory">
NOTE: if we uncomment this section, add something about WAI-ARIA as well. However, I do not believe we need this section. DGK 20160122
<h2>W3C-WAI Guidelines Related to Digital Publishing</h2>
</section>
<section class="introductory">
<h3>WCAG 2.0</h3>
<p>The Web Content Accessibility Guidelines (WCAG) 2.0 [<a href="http://www.w3.org/TR/WCAG20/">WCAG2</a>] is meant for content creators and authoring tool creators. Content that follows WCAG 2.0 will be accessible to users with a wide range of disabilities, presuming that guidelines are also followed by their user agents and assistive technologies.</p>
</section>
<section class="introductory">
<h3>UAAG 2.0</h3>
<p>The User Agent Accessibility Guidelines (UAAG) 2.0 [<a href="http://www.w3.org/TR/UAAG20/">UAAG2</a>] is meant for the developers of user agents (e.g. web browsers and e-readers). A user agent that follows UAAG 2.0 will improve accessibility through its own user interface, through options it provides for rendering and interacting with content, and through its ability to communicate with other technologies, including assistive technologies.</p>
<p>To assist developers of e-readers, the <a href="http://www.w3.org/TR/UAAG20-Reference/">UAAG 2.0 Reference</a> support document needs to contain examples relevant to digital publishing. It has not been within the scope of this Task Force to create a note with some examples for the UAAG team. However, it should be a product of future digital publishing accessibility work.</p>
</section>
<section class="introductory">
<h3>ATAG 2.0</h3>
<p>The Authoring Tool Accessibility Guidelines (ATAG) 2.0 [<a href="http://www.w3.org/TR/ATAG20/">ATAG2</a>] provides guidelines for the developers of authoring tools. An authoring tool that follows ATAG 2.0 will be both more accessible to authors with disabilities (Part A) and designed to enable, support, and promote the production of more accessible web content by all authors (Part B). </p>
<p>To assist developers of authoring tools for digital publishing, the <a href="http://www.w3.org/TR/IMPLEMENTING-ATAG20/">Implementing ATAG 2.0</a> support document needs to contain examples relevant to digital publishing. It has not been within the scope of this Task Force to create a note with some examples for the ATAG team. However, it should be a product of future digital publishing accessibility work.</p>
</section>
-->
<section>
<h2>Audience</h2>
<p>The audience of this document includes involved people creating and modifying existing W3C specifications, especially those oriented around accessibility.</p>
</section>
<section>
<h2>The Gap Between Digital Publishing Issues and W3C Standards</h2>
<p>A gap exists between specific digital publishing industry requirements and W3C standards Working Group efforts to date. Requirements that WAI efforts may address in the future are listed here in order of priority. Additional publishing industry requirements exist, but cannot sufficiently be addressed without further research documented Appendix A. Some suggestions request changes or additions to W3C WAI Specifications and Guidelines. Additional proposals seek changes to existing W3C technique documentation and offer suggestions for further outreach. Where possible, we indicated which of the existing W3C guidelines might be best positioned to address the change.</p>
<section>
<h4>Navigating Within Multiple Documents or Packaged Documents</h4>
<p>Digital publishing use cases exist to allow users to navigate among multiple documents or collections of documents that make up a publication's whole. For example:</p>
<ul>
<li>Bidirectional linking: A user follows a hyperlink from a publication index to a paragraph in middle of chapter 23 and subsequently realizes that the second index entry may have been a better choice. The user must now return to the publication index (very likely a separate HTML document) to access the link to the second index entry.</li>
<li>A publisher wants to test publication accessibility of an ordered collection of documents to assess whether users can access all elements listed in the publication's table of contents - a single document in the collection specific to navigating an ordered collection of HTML documents. The navigation page and the ordered collection of HTML documents make up a single content package.
</li>
</ul>
<p><strong>The Gap: </strong>Individual HTML documents in a package may not all be WCAG-conformant due to the lack of elements such as navigation, but the content package itself is WCAG-conformant because the detailed navigation HTML document is a directory of the entire package. As such, a package could be considered WCAG-conformant, but a non-sighted reader may not be able to identify or access non-WCAG-conformant documents within the package. Content developers did not catch this singular oversight when they were checking the package navigation document for WCAG conformance instead of every document in the package.</p>
<p>Many digital publications are made up of more than one document. A common practice exists to divide every chapter in books into individual HTML files. EPUB 3 titles, for example, are packaged using a specified mechanism enabling navigation to each publication component. Current W3C WAI Specifications and Guidelines provide no treatment or suggestions for navigating through ordered, packaged content documents. Existing W3C WAI Specifications, Guidelines, and most tools related to accessibility assume that the user is encountering a single whole document.</p>
<p><strong>Potential options for addressing the gap:</strong></p>
<ol>
<li>Add discussion of the packaged document use case to W3C WAI Specifications and Guidelines.</li>
<li>Add an author extension that addresses use cases to W3C WAI Specifications and Guidelines.</li>
</ol>
</section>
<section>
<h4>Discoverability</h4>
<p>Digital publications are often distributed through various channels, for instance in online bookstores. These channels are typically aggregators that have almost no control over publications' content and quality. Besides, a single intellectual work can be distributed as several digital editions, with varying quality and accessibility features.</p>
<p>When users want to acquire digital publications, they need to know if the content will be accessible to them. Therefore, it is crucial that accessibility properties of a digital publication exist as metadata, and that such metadata can be made available to any interested party. For instance, an online bookstore would access such metadata to convey the information to users so that they can discover which digital distribution of a title contains the accessible features specific to their needs.</p>
<p><strong>The Gap: </strong>There is no current recommended standard or specification for recording digital publishing metadata stating that a title is accessible and enumerating the properties of the publication that are AT-compatible.</p>
<p><strong>Potential solution for addressing the gap: </strong>Work with W3C WAI community to identify and recommend a mechanism to enable the declaration and discoverability of metadata on a digital publication, notably to describe its accessibility properties.</p>
<p>References:</p>
<ul>
<li>[[SCHEMA-ORG]]</li>
<li>[[WEB-SCHEMAS]]</li>
<li>[[ONIX-EPUBLICATION]]</li>
</ul>
</section>
<section>
<h4>Optimized publications</h4>
<p>Unlike general Web content, some digital publications are legitimately designed and optimized for specific user groups; this is the case of audio or braille books made for persons with print disabilities. These publications target specific reading modalities. By design, they cannot meet the universal accessibility principles identified in WCAG, despite the fact that they are accessible to their intended audience.</p>
<p><strong>The Gap: </strong> Guidelines to author and evaluate optimized, accessible digital publications do not exist.</p>
<p><strong>Potential solution for addressing the gap: </strong>Work with the W3C WAI community and WCAG WG outreach committee to provide guidelines to author and evaluate optimized digital publications, and to convey their nature to users.</p>
</section>
<section>
<h4>Skippability</h4>
<p>A digital publishing use case exists to allow users to "skip" through components as they read. For example, a screen reader user does not want to read page numbers or headers by default. The user does want to read the footnotes when they encounter a footnote callout within the text. Alternately, a mobility-impaired user, reading a textbook on a mobile device, knows that the textbook chapter contains multiple long tables which are difficult to scroll past. The user wants to be able to designate tables as elements which can be skipped or displayed in some minimal form.</p>
<p>Skippability is a common user preference in assistive technology (AT) tools allowing the user to personalize the content read aloud to a very precise specification. Assistive technology users expect to be able to customize which content components get read aloud or displayed to the user. Non-assistive technology users also need access to the capability.
<ul><li>Users expect to be able to navigate or go back to skipped elements at a later time.</li>
<li>Previously-skipped elements must remain discoverable to assistive technology and user agents.</li>
<li>Skippability require support in visual as well as aural presentation; both screenreader and visual users need access to skippable structures.</li>
</ul>
<p><strong>The Gap: </strong>Current W3C WAI accessibility Specifications and Guidelines do not address what would be considered implementation guidance to provide this functionality either to assistive technology users or to non-assistive technology users. We are not aware of any well known implementations within the publishing community.</p>
<p><strong>Potential options for addressing the gap: </strong>Add language to the W3C WAI specifications discussing the need for User agents to implement skippability.</p>
<p><strong>Reference: </strong> DAISY Skippable Structures Recommendation [[DAISY]]</p>
</section>
<section>
<h4>Escapability</h4>
<p>Multiple digital publishing use cases exist allowing readers to move immediately to the next non-contained block element. Moving quickly within text is a particular problem for readers who browse the web and read at high magnification or mobility impaired readers, regardless of device platform. Escapeability require support in visual as well as aural presentation; both screenreader and visual users need access to escapeable structures.</p>
<p>More specifically, a user in the middle of an element of length needs to be able to move to the next sibling or parent with a simple command. Similarly, the user may need to escape back to the previous text block. Examples include:</p>
<ul>
<li> A chemistry book has a long table of each of the elements in the periodic table. The reader has entered the table, and realizes they do not need to see all of the elements in the table, but they do need to read the text immediately afterward. The user needs to get from the table to the next sibling or parent element without endless scrolling.</li>
<li>A user is reading a magazine article and realizes the next item in the article is an inset sidebar of a document containing a multitude of different types of data, including a chart, an image gallery, an infographic, a video, and some text. This information takes up several screens of content at the reader's zoom level. The user wants to escape the sidebar and return to the content after the enclosing container.</li>
<li>A student reading a physics textbook encountered a math equation but has forgotten what the previously introduced symbol X represented. The student would like to return to the previously escaped block element to review the text describing the purpose of symbol X.</li>
</ul>
<p><strong>The Gap: </strong>Current W3C WAI accessibility Specifications and Guidelines do not address what would be considered implementation guidance to provide this functionality either to assistive technology users or to non-assistive technology users.</p>
<p><strong>Potential options for addressing the gap: </strong>Add language to the W3C WAI Specifications and Guidelines discussing the need for User agents to implement escapability.</p>
</section>
<section>
<h4>Page Markers / Pagination</h4>
<p>Multiple digital publishing use cases exist for allowing users to work with and manipulate paged content that does not necessarily flow vertically similar to the content of most web pages. Many electronic publications have intentional correspondence to printed publications. Some electronic publications may have the equivalent of page markers for coordinating specific points in text across multiple editions. Therefore, the concept of page markers/locators is not a throw-back to print publishing.</p>
<p>Specific examples of page marker/pagination use cases include:</p>
<ul>
<li>A magazine publishes both print and online editions. The publisher distributes the online edition as a website (rather than as a standalone EPUB). To boost sales of the magazine's print edition, the publisher would like to provide special interactive features to print subscribers. The interactive features require that readers are easily able to jump to the page marker they're currently reading in the print edition, or to know what page of the print edition corresponds to the website content they are currently viewing.</li>
<li>A high school teacher has assigned a novel, and all the students are reading a particular published edition for convenience. One of the students uses AT and is reading the ebook with AT preferences set to resize and reflow the content. In class, the teacher instructs the students to turn from page 56 to page 53. The reader must also be able to locate pages 56 and 53 to keep pace with the rest of the class.
<p>The student using AT has set the page size on the viewable area of their AT to a particular zoom level, so their paginated view in their ebook reader does not correspond to a page of the print edition. The student remembers they saw something they needed three screens ago and wants to skip back those three screens.</p>
</li>
</ul>
<p><strong>The Gap: </strong> Current W3C WAI Specifications and Guidelines do not contain discussion of the user need to identify and navigate content based on markers (also called locators) that may or may not correspond to printed publication page numbers. Readers need a means of quickly and accurately navigating digital publications by locators corresponding to printed page markers, regardless of whether or not the user has set their preferences to resize or reflow text. Further, the mechanism to support navigating text by locators and page markers should not disrupt continuous reading for students using Aural AT solutions.</p>
<p><strong>Potential options for addressing the gap: </strong>The CSS Paged Media Module Level 3 [[CSS3-PAGE]] describes a method for providing page numbers in the context of a scenario where the text is paginated when sent to a printer from a web page. User agents could implement a similar solution facilitating access to accurate page numbers and pagination.</p>
<p>The W3C WCAG and DPub groups should engage with the Pagination Task Force of the CSS Working Group to determine whether an acceptable, accessible solution for addressing page numbers and pagination already exists.</p>
<p><strong>Potential interim options for addressing the gap: </strong></p>
<ol>
<li>Add language to W3C WAI Specifications and Guidelines implementing a concept corresponding to the EPUB 3 specifications to create print pagination corresponding locators using <code>page-list</code> and <code>pagebreak</code> concepts.</li>
<li>Provide implementation guidance to User Agents instructing the need to enable, where relevant, both distinct concepts of pages (described below), including allowing users to jump to page numbers in either model or view specific pages in either model.</li>
</ol>
<p><strong>Reference: </strong>[[CSS-Paged-Media]] Module Level 3 Page-Margin Boxes</p>
</section>
<section>
<h4>Phonetic spellings of proper nouns and jargon terms</h4>
<p>Multiple digital publishing use cases exist to enable AT solutions to support phonetic spelling of proper nouns and jargon. For example:</p>
<ul>
<li>A chemistry book needs to use the accepted pronunciations of chemistry terms to maximize clarity. It references a pre-existing pronunciation dictionary made available by the American Chemical Society that uses community-agreed-upon standards.</li>
<li>The trade novel THE LIVES OF CHRISTOPHER CHANT by Diana Wynne Jones, in which there is a plot point that a character's name is spelled "Ralph" but pronounced "Rafe," can be correctly encoded using a local pronunciation dictionary.</li>
<li>Reading systems support the pronunciation dictionary reference and expose the data to Accessibility APIs.</li>
</ul>
<p>Publishers need to be able to put in suggested pronunciation for proper nouns, acronyms, and field-specific jargon terms. The Pronunciation Lexicon (PLS) and Speech Synthesis Markup Language [[SSML]] lack widespread adoption, probably because of the lack of tools useful for large-scale publishing production as well as the lack of reading system support.
</p>
<p>The Speech Synthesis Markup Language [[SSML]] is another option for phonetic pronunciations, but it is currently not supported in HTML. EPUB attempted to address this shortcoming through the introduction of [[SSML]] attributes, but the attributes are unique to that format, limited to XHTML and not well supported within it. A solution that similarly simplifies SSML but brings support to all HTML user agents is needed.</p>
<p><strong>The Gap: </strong>Current W3C WAI Specifications and Guidelines have poor implementation with regards to phonetic spelling, probably due to lack of authoring tools, reading system support, and implementation guidance.</p>
<p><strong>References:</strong></p>
<ul>
<li>Pronunciation Lexicon Specification (PLS) [[PRONUNCIATION-LEXICON]]</li>
<li>Speech Synthesis Markup Language (SSML) [[SSML]]</li>
</ul>
</section>
<section>
<h4>Deeply Nested Heading Levels Best Practices</h4>
<p>Digital publishing use cases exist to support encyclopedias and similarly detailed reference works containing many levels of headings.</p>
<p>It is not easy to determine what best practice is for deeply nested headings, headings that go beyond <code><h6></code>. Best Practices should be clearly established and easy to find. Use cases in books are more frequent than other circumstances. This is likeliest to occur if an <code><aside></code> begins with <code><h5></code> or <code><h6></code>.</p>
<p><strong>The Gap: </strong>Current W3C WAI Specifications and Guidelines do not address what are considered implementation guidance to non-assistive technology users. ARIA has heading guidance, but ARIA should be a fallback, only when HTML is inadequate. Furthermore, most content creators are unclear of what it announced to AT when there are nested levels of <code><h#></code>, <code><header></code>, <code><role="header"></code>, and <code><aria-level=#></code>. Clearer documentation of this interaction is necessary.</p>
<p><strong>Potential solution for addressing the gap: </strong>Add specific guidance related to supporting deeply nested heading levels in reference works to W3C WAI Specifications, Guidelines, and Tutorials.</p>
<p><strong>References:</strong></p>
<ul>
<li>Item #3: 15 May 2015 DPub Minutes [[DPub-Minutes-3]]</li>
<li>Using role="heading" to identify headings [[WAI-Wiki]] April-June 2015 [][WAI-IG-Minutes]]</li>
</ul>
</section>
<section>
<h4>Semantic List-Head</h4>
<p>A digital publishing use case exists to support a semantic title or head within a list.</p>
<p><strong>The Gap: </strong>Currently, no clear method of associating a title with a list exists in any W3C specification.</p>
<p>Creating the visual effect of a list containing a semantic title or head can be accomplished using markup wrappers such as <code><div></code>, but list elements (<code><ul></code> and <code><ol></code>) should include titles.</p>
<p>Consider the following simple example:</p>
<pre><ul>
<listtitle>Noble Gases</listtitle>
<li>Helium</li>
<li>Neon</li>
<li>Argon</li>
<li>Krypton</li>
<li>Xenon</li>
<li>Radon</li>
</ul></pre>
<p>It is tempting to use HTML5 h1 – h6 elements or add role="heading", but in both cases the result is unwanted default navigation. This heading should specifically self-identify as lists to screen readers. A potentially useful option would be to include a role value as part of an element called <code>"listtitle"</code> (or something similar). The option to include a semantic title in a list requires support in visual as well as aural presentations; both screen reader and visual users need access to the list header..</p>
</section>
<!-- Main content section -->
</section>
<!-- Appendices -->
<section class='appendix'>
<h1>Future work</h1>
<p>The Digital Publishing Interest Group is not making any recommendations on the following items at this time. They are included to increase awareness of the work we believe still needs to be done for accessibility in the digital publishing space. Existing W3C Working Groups are already addressing some of these points. Others will be investigated by the DPub IG Accessibility TF shortly.</p>
<section>
<h4>Layout's Influence On Comprehension</h4>
<p><strong>Use cases:</strong></p>
<ul>
<li>Use Case: Concrete poetry, such as "The Mouse's Tail" [[MOUSE]] by Lewis Carroll, "Soweto" [[SOWETO]] by Kamau Braithwaite, or "Women" [[WOMEN]] by May Swenson.</li>
<li>Use Case: Puzzles, such as "Headshots" [[HEADSHOTS]], a puzzle which relies on exact location on the page to produce a solution.</li>
</ul>
<p>Comments: There is currently no reasonable, scalable, generalizable and sustainable method to provide information about the layout of text on a page to screen readers and braille displays.</p>
<p>Certain literary styles such as poetry may use the placement of text to convey extra meaning. There is no consistent method for content creators to make this additional information available to a non-visual display such as a screen reader. We have no suggested approaches at this time. More research and investigation is warranted.</p>
<p><strong>Suggestion:</strong> Although a solution is needed, the DPub IG has no good suggestions at this time. More research and investigation is warranted.</p>
<p>Contact:</p>
<ul>
<li>None at this time.</li>
</ul>
<p>References:</p>
<ul>
<li>[[IDPF-Guide-Logical-Reading-Order]]</li>
</ul>
</section>
<section>
<h4>Annotations</h4>
<p>Annotations are a general web requirement, but they are a vital need in the digital publishing industry. These annotations (including: highlights and adding personal notes to a document) must be accessible for creation, editing, and access. The W3C Annotations WG is aware of the requirements of accessibility both in UAs as well as the format.</p>
<p>Because of the importance of annotations in the industry, the DPub Accessibility TF will continue to stay in communication with the W3C Annotation WG and its descendants to address the open issues in this area.</p>
<p><strong>Suggestion:</strong> Communicate regularly with the W3C Annotations WG.</p>
<p>Reference:</p>
<ul>
<li>[[ANNOTATIONS-WG]]</li>
</ul>
</section>
<section>
<h4>Notes (Footnotes, Asides, Author Notes, etc.)</h4>
<p>The W3C recently completed the necessary component of this work, with the new DPub-ARIA 1.0 module. DPub-ARIA 1.0 includes [[DPub-ARIA-FootNote]] and [[DPub-ARIA-FootNotes]]. These roles convey that information is ancillary without conveying information about positioning, allowing authors and user agents to achieve positioning using CSS or scripting while maintaining the flow and navigability of the content.</p>
<p>The Accessibility TF will consider what steps might be taken to publicize the new roles within the digital publishing community.</p>
<p>Contacts:</p>
<ul>
<li>[[DPub-IG]]</li>
<li>[[ARIA-WG]]</li>
</ul>
</section>
<section>
<h4>Positional location of text to indicate different speakers</h4>
<p>Use cases:</p>
<ul>
<li>Use Case: comic strips have different speakers on different sides of the page. </li>
<li>Use Case: poetry </li>
<li>Use Case: different voices for different speakers. </li>
</ul>
<p><strong>Suggestion:</strong> Although a solution may be needed, DPub IG has no good suggestions at this time. More research and investigation is warranted. Possibly all use cases can be addressed with CSS.</p>
<p>Contact:</p>
<ul>
<li>[[READIUM]]</li>
</ul>
<p>References:</p>
<ul>
<li>CSS Speech Module[[CSS3-SPEECH]]</li>
</ul>
</section>
<section>
<h1>Assessments</h1>
<p>Use cases:</p>
<ul>
<li>Adjustable timings needed for accessibility conflict with a proctor's need to control time limits.</li>
<li>Extended descriptions of visual elements must be controlled to provide the test taker with the appropriate level of information, possibly customized by the test taker's individualized accommodations (such as an IEP in the United States).</li>
</ul>
<p>[[ETS]] and members of the IMS Accessibility Task Force are leading the effort to harmonize the IMS QTI/APIP accessibility model with HTML5/ARIA and WCAG. A gap analysis is underway at [[ETS]] and recommendations for enhancements to both guidelines (including techniques and best practices) and standards, such as the addition of new ARIA attributes. The bulk of these recommendations will come from their group; we will coordinate with them as they request. We've done initial outreach.</p>
<p><strong>Suggestion:</strong> The DPub Accessibility Task Force will coordinate with the IMS Assessment Accessibility Task Force</p>
<p>Contacts:</p>
<ul>
<li>[[ETS]]</li>
<li>[[IMS-Global]]</li>
</ul>
<p>References:</p>
<ul>
<li>[[IMS-Global-QTI]]</li>
<li>[[IMS-Global-APIP]]</li>
<li>[[ACCESSIBLE-ONLINE-LEARNING]]</li>
</ul>
</section>
<section>
<h4>Mathematics</h4>
<p>Use cases:</p>
<ul>
<li>Mathematics. Tools such as MathJax [[MATHJAX]], MathQuill [[MATHQUILL]], [[MATHEMATICAL]] and many other tools provide HTML and SVG rendering of mathematical content.</li>
<li>Chemistry. ProgressiveAccess [[PROGRESSIVE]], Avogadro [[AVOGADRO]], jchempaint [[JCHEMPAINT]] and many other tools render chemical information as SVG.</li>
</ul>
<p>There is currently no reasonable, scalable, generalizable and sustainable method to provide information about mathematical rendering using HTML with CSS or SVG to screen readers and braille displays.</p>
<p>While MathML is part of HTML5, virtually all mathematical and scientific content on the web is rendered using HTML (with CSS) and SVG. While these standards are sufficient for visual rendering, there is no consistent method for content creators to make mathematical and scientific information available to a non-visual display such as a screen reader.</p>
<p>The newly created [[Math-on-Webpages-CG]] Community Group plans to address rendering issues as well as accessibility related issues, focusing on a bottom-up approach of improving the web platform overall to help improve current and future technologies.</p>
<p><strong>Suggestion: </strong>The DPub IG could follow and support the efforts of the math-on-webpages Community Group and encourage a joint Task Force between the Community Group and the W3C's ARIA WG to investigate potential solutions such as a mathematics/STEM-related ARIA module.</p>
<p>Contact:</p>
<ul>
<li>[[Math-on-Webpages-CG]]</li>
</ul>
</section>
</section> <!-- end future work -->
<section class='appendix'>
<h1>Gap Analysis</h1>
<p>The Accessibility Task Force of the Digital Publishing Interest Group performed a gap analysis identifying the needs of the digital publishing industry and WCAG. We did not perform a gap analysis for any other W3C standards. The meaningful results of the gap analysis have been broken out into this Note. However, the full gap analysis of the various techniques are refenced here which link out to the respective wiki tables. Here the team investigated each technique, whether or not it is a requisite for digital publishing, and indicated in initial comments what should be the jumping off point for discussion in the group.</p>
<a href="https://github.com/w3c/dpub-accessibility/wiki/DPUB-Specific-WCAG-General-Techniques">DPUB Specific WCAG General Techniques</a>
<p><a href="https://github.com/w3c/dpub-accessibility/wiki/DPUB-Specific-WCAG-HTML-Techniques">DPUB Specific WCAG HTML Techniques</a></p>
<p><a href="https://github.com/w3c/dpub-accessibility/wiki/DPUB-Specific-WCAG-CSS-Techniques">DPUB Specific WCAG CSS Techniques</a></p>
<p><a href="https://github.com/w3c/dpub-accessibility/wiki/DPUB-Specific-WCAG-Client-Side-Scripting">DPUB Specific WCAG Client Side Scripting</a></p>
<p><a href="https://github.com/w3c/dpub-accessibility/wiki/DPUB-Specific-WCAG-Server-Side-Scripting">DPUB Specific WCAG Server Side Scripting</a></p>
<p><a href="https://github.com/w3c/dpub-accessibility/wiki/DPUB-Specific-WCAG-SMIL-Techniques">DPUB Specific WCAG SMIL Techniques</a></p>
<p><a href="https://github.com/w3c/dpub-accessibility/wiki/DPUB-Specific-WCAG-Plain-Text-Techniques">DPUB Specific WCAG Plain Text Techniques</a></p>
<p><a href="https://github.com/w3c/dpub-accessibility/wiki/DPUB-Specific-WCAG-ARIA-Techniques">DPUB Specific WCAG ARIA Techniques</a></p>
<p><a href="https://github.com/w3c/dpub-accessibility/wiki/DPUB-Specific-WCAG-Flash-Techniques">DPUB Specific WCAG Flash Techniques</a></p>
<p><a href="https://github.com/w3c/dpub-accessibility/wiki/DPUB-Specific-WCAG-Silverlight-Techniques">DPUB Specific WCAG Silverlight Techniques</a></p>
<p><a href="https://github.com/w3c/dpub-accessibility/wiki/DPUB-Specific-WCAG-PDF-Techniques">DPUB Specific WCAG PDF Techniques</a></p>
<p><a href="https://github.com/w3c/dpub-accessibility/wiki/DPUB-Specific-Common-Failures">DPUB Specific Common Failures</a></p>
<p><a href="https://github.com/w3c/dpub-accessibility/wiki/DPUB-Specific-Techniques">DPUB Specific Techniques</a></p>
<p><strong>Reference: </strong>[[DPub-Accessibility-Wiki]]</p>
</section> <!-- end gap analysis -->
<section class='appendix'>
<h1>Relevant Work in Development Outside the W3C</h1>
<p>Some open specifications under development or maintained outside the W3C have great relevance to the accessibility in the digital publishing sector. Members of the W3C involved in accessibility within digital publishing need to be aware of work happening in these spaces. Here we describe some key projects that are relevant to our work.</p>
<ol>
<li><a href="#epub"></a></li>
<li><a href="#diagrammar"></a></li>
<li><a href="#pdf"></a></li>
</ol>
<section>
<h1>EPUB</h1>
<section>
<h2>EPUB's relevance to the W3C and accessible digital publishing</h2>
<p>EPUB is quickly becoming one of the de facto standards in digital publishing and is gaining global traction. Some existing reading systems read EPUB books. This standard is actively being updated and improved. EPUB is based on HTML5 and adheres to the WCAG accessibility standards.</p>
<h2>Maintainers of the specification</h2>
<p>[[IDPF]] (International Digital Publishing Forum) created and maintains the EPUB® standard.</p>
<p>Contact:</p>
<ul>
<li>[[IDPF-CONTACT]]</li>
</ul>
<h2>Historical Context</h2>
<p>Beginning with EPUB 3.0, the primary accessible publishing standard, DAISY DTBook and the primary commercial publishing format merged. DAISY’s Digital Talking Book [[DAISY-DTD]] is an XML-based file format and puts an emphasis on structural encoding to enable reading for the visually impaired audience. EPUB 2 allowed DTBook as an alternate syntax. The EPUB 3 specification merged DAISY and EPUB, making accessibility considerations a concern for all publishers, authors, and readers. The EPUB 3.0.1 specification is available at [[EPUB3]]. One of the features of this relationship is the [[IDPF-EPUB-Structure-Semantics-Vocabulary]], a namespaced vocabulary that enables semantic inflection of HTML elements. In 2015, several of these terms have been transformed into prefixed ARIA roles in [[DPub-ARIA-1.0]].</p>
<p>The IDPF and W3C Digital Publishing Interest Group work closely together on many issues, including broadening the definition of Web Accessibility to include long-form content. The Digital Publishing Interest Group’s Charter includes advancing EPUB 3 as one of the goals. Among the success criteria are providing advice to the IDPF EPUB 3.1 Working Group and advancing what is now called Portable Web Publications [PWP], a vision for the convergence of future of digital documents and the Web. Integrating the accessibility functionality that is native to the Web with the additions that DAISY and the IDPF have created is part of that vision.</p>
<h2>References:</h2>
<ul>
<li>[[DAISY-DTD]]</li>
<li>EPUB 3.0.1 Specification [[EPUB3]]</li>
<li>EPUB 3.1 Work Plan [[EPUB3.1]]</li>
<li>Digital Publishing WAI-ARIA Module 1.0 [[DPub-ARIA-1.0]]</li>
<li>IDPF's GitHub Repository [[IDPF-GITHUB]]</li>
</ul>
</section> <!-- end epub relevance-->
</section> <!-- end epub -->
<section class='appendix' id='diagrammar'>
<h1>Diagrammar</h1>
<h2>Diagrammar's relevance to the W3C and accessible digital publishing</h2>
<p>The W3C standards bodies have developed multiple ways of creating extended descriptions for certain page elements, available for accessibility purposes. WAI-ARIA 1.1 draft proposes using ARIA-DETAILS and ARIA-LINKTYPE, and HTML5 has longdesc [[HTML-LONGDESC]]. Although the proposed ARIA changes address most of digital publishing's use cases, there is still need to have these extended descriptions accessible to those who may not be using assistive technology. [[DIAGRAMMAR]] is being developed to address this set of use cases.</p>
<p>The Diagrammar team intends to support a [[DIAGRAMMAR]] XML data to HTML transformation for presentation. Therefore, it will be useful for ongoing communication to continue.</p>
<h2>Specification Maintainance</h2>
<p>[[DIAGRAM-Center]], a [[BENETECH]] initiative, in partnership with the WGBH National Center for Accessible Media and the US Fund for [[DAISY]], develops [[DIAGRAMMAR]].</p>
<p>Contacts:</p>
<ul>
<li>[[DIAGRAM-Center]]</li>
</ul>
<h2>Historical Context</h2>
<p>In the early days of the web, there was recognition that images were an obstacle to persons who are blind and others who could not process the visual information. Today, we find that there are much more types of information objects that are not perceivable to persons with disabilities. Furthermore, publishers and other content creators recognize that alternative mechanisms for conveying information can benefit everybody. These extended descriptions not only pertain to images but any web element that is visually complex, requiring a description in more detail; the DIAGRAM Center hosts [[DIAGRAMMAR]] use cases for extended description information in multiple formats. Alternative representations may be required, and we need a way to link a specific web element to multiple representations be it an extended description, simplified description, or a tactile or auditory representation of the element.</p>
<p>[[DIAGRAMMAR]] is an XML framework to hold multiple extended description types, to make a wide range of content types accessible: images, tables, charts, animations, 3D animations, etc. [[DIAGRAMMAR]] defines a data model for extended descriptions and associated metadata. It provides a structured, standard way for modeling extended descriptions data, including different modality types for extended descriptions.</p>
<h2>References:</h2>
<ul>
<li>[[DIAGRAM-Center]]</li>
<li>[[DIAGRAMMAR]]</li>
<li>[[ANSI-NISO-Z39.98-2012]] "Authoring and Interchange Framework for Adaptive XML Publishing Specification."</li>
</ul>
</section> <!-- end DIAGRAMMAR -->
<section class='appendix' id='pdf'>
<h1>PDF</h1>
<p>Any current discussion of digital publishing and accessibility should reference PDF and the accessibility efforts surrounding that technology.</p>
<h2>Historical perspective</h2>
<p>PDF was released in 1992 and through the 1990’s quickly became the defacto standard as a replacement for "camera ready copy." PDF eliminated the problems associated with differences between computers and printers. One could finally take a single PDF file, print it anywhere and it would look identical. Publishers would take high resolution PDF pages and provide them to their printing houses for printing and binding; in fact, this remains the primary mechanism used today.</p>
<p>While printing of PDFs was a primary use case, the ability to be able to view the content consistently on any screens (just as on printers) became very popular and led to its adoption in many industries such as legal, engineering and government forms. These industries, combined with the printing industry, brought PDF to international standardization through the ISO as ISO 32000-1:2008.</p>
<p>This ability to be able to digitally represent both born-digital and paper-based content and distribute it through either formal or ad-hoc means is considered by some to be a form of digital publishing.</p>
<h2>Accessibility in PDF</h2>
<p>Unfortunately, PDF was not designed with accessibility in mind. While a PDF could be presented on a computer screen, Assistive Technology (AT) could not dependably read the PDF. In short, PDF was inaccessible to persons who are blind.</p>
<p>Over the years, PDF has added many features to enable greater accessibility (starting with PDF 1.3) in the form of Tagged PDF. This work was done in collaboration with the W3C and the WCAG working group and led to the publication of “[[PDF-Techniques-for-WCAG-2.0]]”</p>
<h2>PDF/UA</h2>
<p>PDF/Universal Accessibility, commonly called PDF/UA is the informal name for ISO 14289, the International Standard for accessible PDF technology. PDF/UA became an ISO Standard on 15 July 2012. The latest release, PDF/UA Part 1, was approved as an ISO Standard on 18 December 2014. This standard specifies how to create accessible PDF files, create compliant PDF readers and also AT devices. The combination of the three providing a rich ecosystem for accessible PDF.</p>
<p>The adoption of PDF/UA has been slow, probably because of the lack of authoring tools, reading system interactions with AT, and general lack of training needed to add the additional tagging necessary to meet PDF/UA.</p>
<h2>References:</h2>
<ul>
<li>[[PDF-Techniques-for-WCAG-2.0]]</li>
<li>[[PDF-UA]]</li>
</ul>
</section> <!-- end DIAGRAMMAR -->
</section> <!-- end outside standards -->
<section class='acknowledgments'>
<h1>Acknowledgments</h1>
<dl>
<dt>Contributors:</dt>
<dd>Kathy Alley</dd>
<dd>Alistair Campbell</dd>
<dd>Bo Campbell</dd>
<dd>Michael Cooper (WAI representative)</dd>
<dd>Romain Deltour</dd>
<dd>Matt Garrish</dd>
<dd>Deborah Kaplan (co-chair)</dd>
<dd>Jean Kaplansky</dd>
<dd>Susann Keohane</dd>
<dd>George Kerscher</dd>
<dd>Peter Krautzberger</dd>
<dd>Brijesh Kumar</dd>
<dd>Ivan Herman</dd>
<dd>Charles LaPierre (co-chair)</dd>
<dd>Mia Lipner</dd>
<dd>Livio Mondini</dd>
<dd>Liam Quin</dd>
<dd>Leonard Rosenthol</dd>
<dd>Tzviya Siegman</dd>
<dd>Avneesh Singh</dd>
<dd>Jeanne Spellman (WAI representative)</dd>
</dl>
</section>
</body>
</html>