-
Notifications
You must be signed in to change notification settings - Fork 6
/
Copy pathindex.html
2111 lines (1868 loc) · 75.4 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
<!DOCTYPE html>
<html xmlns="http://www.w3.org/1999/xhtml" lang="en-US"
xml:lang="en-US">
<head>
<meta charset="utf-8" />
<title>Accessibility Metadata Display Guide for Digital Publications
2.0</title>
<script src="https://www.w3.org/Tools/respec/respec-w3c"
class="remove" defer="defer"></script>
<script class="remove">
// <![CDATA[
var respecConfig = {
group: "publishingcg",
specStatus: "CG-DRAFT",
noRecTrack: true,
latestVersion: "https://www.w3.org/publishing/a11y/UX-Guide-metadata/principles/",
edDraftURI: "https://w3c.github.io/publ-a11y/a11y-meta-display-guide/2.0/draft/guidelines/",
canonicalURI: "https://www.w3.org/publishing/a11y/UX-Guide-metadata/principles/",
editors: [
{
"name": "Charles LaPierre",
"company": "Benetech",
"companyURL": "http://www.benetech.org",
"w3cid": 72055
},
{
"name": "Gregorio Pellegrino",
"company": "Fondazione LIA",
"companyURL": "https://fondazionelia.org",
"w3cid": 97111
},
{
"name": "Gautier Chomel",
"company": "EDRLab ",
"companyURL": "https://www.edrlab.org",
"w3cid": 136660
},
{
"name": "George Kerscher",
"company": "DAISY Consortium",
"companyURL": "https://daisy.org/",
"w3cid": 1460
}
],
processVersion: 2020,
includePermalinks: false,
permalinkEdge: true,
permalinkHide: false,
diffTool: "http://www.aptest.com/standards/htmldiff/htmldiff.pl",
github: {
repoURL: "https://github.com/w3c/publ-a11y/",
branch: "main"
},
localBiblio: {
"iso14289-1": {
"title": "ISO 14289-1:2024: Document management applications — Electronic document file format enhancement for accessibility — Part 1: Use of ISO 32000-1 (PDF/UA-1)",
"href": "https://www.iso.org/standard/82278.html",
"publisher": "ISO"
},
"iso14289-2": {
"title": "ISO 14289-2:2024: Document management applications — Electronic document file format enhancement for accessibility — Part 2: Use of ISO 32000-2 (PDF/UA-2)",
"href": "https://www.iso.org/standard/64599.html",
"publisher": "ISO"
},
"onix": {
"title": "ONIX for Books 3.0",
"href": "https://www.editeur.org/8/ONIX/"
}
}
};
// ]]>
</script>
<style>
.responsive {
width: 100%;
height: auto;
}
.fake-issue {
padding: .5em;
border: .5em;
border-left-style: solid;
page-break-inside: avoid;
margin: 1em auto;
}
.fake-issue {
border-color: #e05252;
border-color: var(--issue-border);
background: #fbe9e9;
background: var(--issue-bg);
color: black;
color: var(--issue-text);
counter-increment: issue;
overflow: auto;
}
.fake-issue::before,
.fake-issue>.marker {
color: #831616;
color: var(--issueheading-text);
}
.fake-issue::before,
.fake-issue>.marker {
text-transform: uppercase;
padding-right: 1em;
}
.fake-issue a.respec-gh-label {
padding: 5px;
margin: 0 2px 0 2px;
font-size: 10px;
text-transform: none;
text-decoration: none;
font-weight: 700;
border-radius: 4px;
position: relative;
bottom: 2px;
border: none;
display: inline-block;
}
</style>
</head>
<body>
<section id="abstract">
<p>The accessibility of a publication is useful to know
regardless of a person's abilities, as features such
as the ability to make visual adjustments make for a better
reading experience for everybody. These guidelines
document a shared framework for presenting publication
accessibility metadata declarations in a
user-friendly manner — to offer the information to end users
in a way that is easy to understand
regardless of their technical knowledge and is consistent
across different publications and different
digital catalogs. </p>
</section>
<section id="sotd"></section>
<section id="intro">
<h2>Introduction</h2>
<p>Reading a digital publication is a very personal experience.
For most people this is routine, and little
consideration is given to how the title was obtained before
it is read. Users may go to a bookstore or library,
search for the title to purchase online, or have the title
selected for them by an instructor for a
class.</p>
<p>Now consider that the person is blind and relies on assistive
technology. The user needs that technology
to assist them in the purchase process as well as to read
the e-book. The person may wonder: will
the screen reader work with this title; are there image
descriptions that will be spoken to describe
these images; are there page numbers which are accessible;
is the reading order correct so a caution will be announced
before reading the paragraph which could be dangerous? All
of these accessibility concerns are potential issues
consumers have when trying to purchase and ultimately read a
digital publication in any format.</p>
<p>The good news is more and more publishers are creating
digital publications that are Born Accessible (i.e.,
accessible from the outset, not fixed later) and getting the
accessibility validation or audit done by
independent organizations.</p>
<section id="terminology">
<h3>Terminology</h3>
<p>There are several terms used in these guidelines that
should be defined for clarity:</p>
<dl>
<dt><dfn>digital publication</dfn></dt>
<dd>
<p>The term digital publication is used in this
document to refer to publications produced in
any number of digital formats. Digital
publications are not limited to books, but
encompass any written, visual, or audio work
distributed and read in digital form.</p>
<p>Some examples of digital publications include
ebooks, audiobooks, manga, comic books,
journals, digital textbooks, picture books, and
children's picture books with accompanying
audio. The formats they come in include EPUB,
PDF, and Digital Talking Books (DTB).</p>
</dd>
<dt><dfn>dynamic braille</dfn></dt>
<dd>
<p>The term dynamic braille is used to denote
content that is generated as braille on the fly,
as opposed to preformatted digital braille
formats. This dynamic rendering of
content is sometimes referred to as electronic
braille or refreshable braille.</p>
<p>Dynamic braille is typically rendered on a
separate device from the reading system, one
with
pop-up pins to present the braille on a tactile
screen. These devices, commonly referred to as
refreshable braille displays, can be attached to
a personal computer, or they may be a
self-contained multipurpose note taker with a
refreshable braille display.</p>
</dd>
<dt><dfn>read aloud speech</dfn></dt>
<dd>
<p>The term read aloud speech is used to denote
content that is generated into synthetic speech
on the fly, as opposed to prerecorded narration.
Read aloud functionality is often a feature
of reading systems, but can be provided by a
separate assistive technology.</p>
</dd>
<dt><dfn>reading system</dfn></dt>
<dd>
<p>All digital publications require a reading system
to present the publication to the end user.
Reading Systems may be Apps that run on a smart
phone or tablet. There are Reading Systems which
are applications that run on personal computers.
There are also Reading Systems that are
integrated in to dedicated devices devoted to a
single purpose, for presenting a publication.
There are even skills that run on smart speakers
that can be considered Reading Systems.</p>
</dd>
</dl>
</section>
</section>
<section id="general-overview">
<h2>General overview</h2>
<p>These guidelines help those who wish to render accessibility
metadata directly to users understand how to
represent the accessibility claims inherent in
machine-readable accessibility metadata in a
user-friendly User Interface / User Experience (UI/UX). This
document targets implementers such as
bookstores, libraries, retailers, distributors etc. Content
creators will benefit from reading these guidelines and
are encouraged to follow <a
href="https://www.w3.org/TR/epub-a11y-11/">EPUB
Accessibility 1.1
Conformance and Discoverability Requirements section and
its techniques.</a></p>
<div class="note">
<p>This document presents high-level guidelines without
going into technical issues related to the
different metadata standards in the publishing industry.
</p>
<p>Therefore, <a href="#techniques">techniques are
available</a> that illustrate to developers how to
retrieve data to show the information outlined in this
document.</p>
</div>
<p>Metadata found either inside a digital publication or in a
corresponding external record may have
important accessibility claims that help end users find and
determine if the publication can meet their
specific accessibility needs.</p>
<p>This accessibility metadata uses controlled vocabularies to
allow it to be extracted and displayed uniformly across
different publications and localized to different user
interface languages. The one exception is the accessibility
summary, which allows accessibility statements that are
unique to a publication and that adds information not
covered by other metadata entries.</p>
<p>One important aspect is that the role of the Accessibility
Summary metadata has changed in the latest
version of the EPUB Accessibility specification, so a more
in-depth analysis in the <a
href="#accessibility-summary">Accessibility summary</a>
section is recommended.</p>
<p>This document offers guidance on how to aggregate and display
claims inherent in metadata to end users;
these are not strict guidelines, but suggestions for
providing a consistent experience for users through
different portals. Different implementers may choose to
implement these guidelines in a slightly
different way. Some examples can be seen in the <a
href="#implementations">Implementations</a> section
of the document.</p>
<section id="accessibility-claims">
<h2>Accessibility claims and declarations</h2>
<p>When presenting accessibility metadata provided by the
publisher, it is suggested that the section is
introduced using terms such as "claims" or
"declarations." This heading should clearly convey to
the
end user that the information comes directly from the
publisher and represents the accessibility
information that the publisher intends to communicate.
</p>
</section>
<section id="processing-guide">
<h2>Metadata processing overview</h2>
<p>The following diagram depicts how these guidelines relate
to the format-specific techniques in the
process of receiving and displaying accessibility
metadata.</p>
<img class="responsive" src="media/MetadataProcessing.png"
aria-details="ecosystem"
alt="Outline of the processing for EPUB, PDF, ONIX and MARC metadata. Description follows." />
<div class="note">
<p>Work on integrating PDF and MARC is ongoing. The
diagram and text of this section will be updated
in future versions as the related documents are
finalized.</p>
</div>
<p>The diagram categorizes two ways that metadata
accompanies a publication. In the first are digital
publication formats that directly embed accessibility
metadata (EPUB and PDF). In the second are
external metadata record formats (ONIX and MARC) that
accompany a digital publication as it moves
through the supply chain.</p>
<p>In some cases, a digital publication may include both
internal and external metadata (e.g., an EPUB
could have accessibility metadata in it package document
and also be provided to a vendor with an
ONIX record). In these cases, vendors and reading system
developers determine for themselves which
set of metadata they will use to display to users.</p>
<div class="note">
<p>This guide assumes the metadata is already in one of
the formats described in the diagram, but
depending on how the metadata is submitted it may
need to be transformed. For example, if a vendor
prefers to handle only ONIX metadata for display
Then they would need to preprocess the metadata
embedded in an EPUB or PDF to create the ONIX.</p>
<p>The process of transforming metadata is not it scope
for this document nor is how to reconcile
metadata when it is provided in multiple forms. The
guide assumes any processing has already
occurred. For information on mapping between
formats, refer to the <a
href="https://w3c.github.io/publ-a11y/drafts/a11y-crosswalk-MARC/">Accessibility
Properties
Crosswalk</a>.</p>
</div>
<p>The next level of the diagram depicts the encoding
standards expected for each format. This guide
assumes that the metadata conforms to a recognized
standard, otherwise it would be difficult to
anticipate and process the incoming information for
users:</p>
<ul>
<li>For EPUB, the EPUB Accessibility standard
[[epub-a11y-11]] defines required and recommended
metadata for accessible publications. Guidance on
applying this metadata is found in the EPUB
Accessibility techniques [[epub-a11y-tech-11]].</li>
<li>For ONIX, the accessibility characteristics of the
corresponding digital publication are
expressed using <a
href="https://ns.editeur.org/onix/en">code
lists</a> [[onix]], and guidance
on applying these values is defined in the
application note <a
href="https://www.editeur.org/files/ONIX%203/APPNOTE%20Accessibility%20metadata%20in%20ONIX%20(advanced).pdf">Providing
accessibility metadata in ONIX (advanced)</a>.
</li>
<li>For PDF, the PDF/UA standard
[[iso14289-1]][[iso14289-2]] and <a
href="https://pdfa.org/wtpdf/">Well-Tagged PDF
guide</a> define how to describe accessibility
metadata.</li>
</ul>
<p>Knowing how the metadata is encoded and how it is
expressed, the next stage of processing is to use
the algorithms defined in the respective techniques
documents to discover and translate the
information into human-readable statements. These
documents are intended primarily for developers,
to help them with the specific processing of the
metadata markup grammars.</p>
<p>Finally, this document is shown at the last stage of
processing, as it defines the purpose of each
piece of metadata in more detail and prioritizes the
display for readers.</p>
</section>
<section id="techniques">
<h3>Metadata techniques</h3>
<p>To assist developers in implementing these guidelines,
in-depth notes are available to explain how to
extract information from publishing industry metadata
standards.</p>
<p>At the time of publishing this document the available
techniques for metadata standards are:</p>
<ul>
<li>
<p><a href="../techniques/epub-metadata/index.html">EPUB
Accessibility Metadata</a></p>
</li>
<li>
<p><a href="../techniques/onix-metadata/index.html">ONIX
Accessibility Metadata</a></p>
</li>
</ul>
<div class="note">
<p>Publishers update their ONIX records as needed. We
expect "unknown" accessibility metadata may be
initially provided but may change as more
information becomes available. For this reason,
implementors should be prepared to update the
accessibility metadata as new ONIX feeds are made
available.</p>
</div>
</section>
</section>
<section id="general-info">
<h2>General information</h2>
<p>To solve the problem of displaying the accessibility metadata
in a human readable form, vendors will
determine their correct statement to display (from the
Accessibility Metadata Display Guide for Digital
Publications) by parsing the metadata and using the
appropriate Display Techniques document. </p>
<p>The product details provide precious information about the
usability of the e-book in relation to specific
user needs. The following information should always be
displayed:</p>
<ul>
<li> File format (EPUB 2 or 3, PDF, MP3, Audiobook, etc.)
</li>
<li> Protection measure or lack thereof </li>
<li> Name of the publishing house </li>
<li> Main language of the content </li>
</ul>
<section>
<h3>Why this information is important for accessibility</h3>
<ul>
<li> The file format gives a strong indication of
accessibility: a PDF does not allow for typography
modification, EPUB 2 is
deprecated, an EPUB 3 supports page navigation and
better structural semantics; an MP3 format audiobook
will be
less structured than an Audiobook, etc. </li>
<li> The protection measure may block assistive
technologies such as screen readers. In addition,
many specific eReading devices such as DAISY readers
or Braille note takers are not equipped to read
encrypted files. </li>
<li> The name of the publishing house can highlight the
efforts it has made in terms of
accessibility. </li>
<li> The main language of the content enables readers to
be confident that they will be able to read
with their Assistive Technology that uses
synthesized voice or the corresponding Braille
translation table
for the language. </li>
</ul>
</section>
</section>
<section id="order-of-key-information">
<h2>Key accessibility information</h2>
<section id="intro-key-info" class="introductory">
<h3>Introduction to key accessibility information</h3>
<p>When focusing on the accessibility of any digital
publication, several areas of key information come to
mind:</p>
<ul>
<li>People who need to adjust the visual presentation
want to know if they can enlarge the text,
which is essential for low vision users. People with
dyslexia must be able to select the font
and adjust the foreground, background, and line
spacing and length. People with low vision and
dyslexia
represent the largest percentage of the
print-disabled population.</li>
<li>People who use a screen reader need to know if all
the content in the title will be accessible
to them. When images have text descriptions (alt
text), they are assured that they will be not
missing out on essential information. Blind users
will greatly benefit from this information as
well as individuals who use the read aloud feature
in Reading Systems.</li>
<li> People who are selecting materials for public
institutions such as libraries or schools need
to know if the content conforms to accepted
standards.</li>
</ul>
<p>This is why these guidelines recommend that the following areas
of key information should be
displayed:</p>
<ul>
<li>Visual adjustments</li>
<li>Support for nonvisual reading</li>
<li>Conformance</li>
</ul>
<p>The other areas provide details about specific
features or shortcomings in publications. It is
expected that these other areas of key information will
give people what they need to make an
informed choice to read a particular e-book.</p>
<div class="note"><p>When no accessibility metadata is being provided by the publisher, making a statement that the item is "unknown" or "The metadata was not provided" creates a negative statement, which the publisher did not make. The distributer may not be allowed to show statements the publisher did not make. </p></div>
<div class="note">
<p>This document does not define the order in which to
show the key accessibility information; each
implementer can decide the preferred order for
showing the accessibility information that
follows.</p>
<p>In this document are examples of important metadata
that is expected to be in a wide range of
publications. However, we do not have examples of
all possible features that the metadata can
express. The techniques have more values than are
shown in the examples.</p>
</div>
</section>
<section id="visual-adjustments">
<h3 data-localization-id="visual-adjustments-title">Visual
adjustments</h3>
<div class="note">
<p>This key information should be displayed, even
if there is no metadata (See the examples
where the metadata is not known). </p>
</div>
<p>Indicates if users can modify the appearance of the text
and the page layout according to the
possibilities offered by the reading system.</p>
<p>This field answers whether visual adjustments are
possible, not possible, or unknown.</p>
<p>Readers with visual impairments or cognitive disabilities
need the ability to change the color of
text and its background (contrast), the font family and
font size used, as well as spacing between
letters, words, sentences, or paragraphs.</p>
<p><!--this one might be moved to the techniques-->Knowing
that a publication can reflow to fit the
reading system's display area is not sufficient to know
that modifications to the font, spacing, and
colors are possible or that the changes will not cause
other readability issues (e.g., text being
clipped by its container).</p>
<section id="va-examples">
<h4>Examples</h4>
<p>The examples are provided as lists of possible
descriptive and compact explanations for
flexibility of adoption.</p>
<aside class="example" title="Descriptive explanations">
<ul>
<li data-localization-id="visual-adjustments-modifiable"
data-localization-mode="descriptive">
Appearance of the text and page layout can
be
modified according to the capabilities of
the reading system (font family and font
size,
spaces between paragraphs, sentences, words,
and letters, as well as color of background
and text)</li>
<li data-localization-id="visual-adjustments-unmodifiable"
data-localization-mode="descriptive">Text
and page layout cannot be modified as the
reading experience is close to a print
version, but reading systems can still
provide zooming options</li>
<li data-localization-id="visual-adjustments-unknown"
data-localization-mode="descriptive">
Appearance modifiability not known</li>
</ul>
</aside>
<aside class="example" title="Compact explanations">
<ul>
<li data-localization-id="visual-adjustments-modifiable"
data-localization-mode="compact">Appearance
can be modified</li>
<!--if Display transformability is present-->
<li data-localization-id="visual-adjustments-unmodifiable"
data-localization-mode="compact">Appearance
cannot be modified</li>
<!--if display transformability is not present and text on visual is present-->
<li data-localization-id="visual-adjustments-unknown"
data-localization-mode="compact">Appearance
modifiability not known</li>
<!--if neither display transformability nor text on visual are presents-->
</ul>
</aside>
</section>
<section id="va-techniques">
<h4>Display techniques for Visual adjustments support
</h4>
<p>Specific techniques for meeting this principle are
defined in the following documents:</p>
<ul>
<li><a
href="../techniques/epub-metadata/index.html#visual-adjustments">EPUB
Accessibility:
Visual Adjustments</a></li>
<li><a
href="../techniques/onix-metadata/index.html#visual-adjustments">ONIX:
Visual
Adjustments</a></li>
</ul>
</section>
</section>
<section id="supports-nonvisual-reading">
<h3 data-localization-id="nonvisual-reading-title">Support
for nonvisual reading</h3>
<div class="note">
<p>This key information should be displayed, even
if there is no metadata (See the examples
where the metadata is not known). </p>
</div>
<p>Indicates whether all content required for comprehension
can be consumed in text and therefore is
available to reading systems with [=read aloud speech=]
or [=dynamic braille=] capabilities.</p>
<p>This field answers whether nonvisual reading is possible,
not possible, or unknown.</p>
<p>Digital publications with essential content included in
non-textual form (such as images, photographs, graphs,
tables or
equations presented as images, videos, etc.) must
include textual alternatives to ensure that users
reading with other senses than sight (mainly auditory
and tactile) have access to the same
information as visual readers. These textual
alternatives can include alt text on images, extended
descriptions,
transcripts, captions, etc. depending on the nature of
the nonvisual content.</p>
<section id="nv-examples">
<h4>Examples</h4>
<p>The examples are provided as lists of possible
descriptive and compact explanations for
flexibility of adoption.</p>
<aside class="example" title="Descriptive explanations">
<ul>
<li data-localization-id="has-alt-text"
data-localization-mode="descriptive">Has alt
text on images</li>
<li data-localization-id="nonvisual-reading-readable"
data-localization-mode="descriptive">All
content can be read as read aloud speech or
dynamic braille</li>
<li data-localization-id="nonvisual-reading-may-not-fully"
data-localization-mode="descriptive">
Portions of the content may not be readable
as read aloud speech or dynamic braille</li>
<li data-localization-id="nonvisual-reading-not-fully"
data-localization-mode="descriptive">Not all
of the content will be readable as read
aloud speech or dynamic braille</li>
</ul>
</aside>
<aside class="example" title="Compact explanations">
<ul>
<li data-localization-id="has-alt-text"
data-localization-mode="compact">Has alt
text</li>
<li data-localization-id="nonvisual-reading-readable"
data-localization-mode="compact">Readable in
read aloud or dynamic braille</li>
<li data-localization-id="nonvisual-reading-may-not-fully"
data-localization-mode="compact">May not be
fully readable in read aloud or dynamic
braille</li>
<li data-localization-id="nonvisual-reading-not-fully"
data-localization-mode="compact">Not
fully readable in read aloud or dynamic
braille</li>
<!--To be Confirmed (see https://github.com/w3c/publ-a11y/issues/367)<li data-localization-id="nonvisual-reading-unknown" data-localization-mode="compact">Not known if readable in read aloud and braille</li>-->
</ul>
</aside>
</section>
<section id="nv-techniques">
<h4>Display techniques for nonvisual reading support
</h4>
<p>Specific techniques for meeting this principle are
defined in the following documents:</p>
<ul>
<li><a
href="../techniques/epub-metadata/index.html#supports-nonvisual-reading">EPUB
Accessibility: Support for nonvisual
reading</a></li>
<li><a
href="../techniques/onix-metadata/index.html#supports-nonvisual-reading">ONIX:
Support
for nonvisual reading</a></li>
</ul>
</section>
</section>
<section id="conformance-group">
<h3 data-localization-id="conformance-title">Conformance
</h3>
<div class="note">
<p>This key information should be displayed, even
if there is no metadata (See the examples
where the metadata is not known). </p>
</div>
<p>Identifies whether the digital publication claims to meet
internationally recognized conformance
standards for accessibility.</p>
<p>Conformance metadata often uses terminology that most
people will not understand, and therefore <a
href="#conf-statements">simple statements</a> should
be provided when EPUB accessibility and
WCAG levels are identified.</p>
<p>If the publication does not include a conformance claim,
the statement should indicate that the
publication does not include a conformance statement.
</p>
<p>In most cases, people will want to know more about the
conformance and certification of the
publication. The certifying organization should be
identified along with their credentials and
placed immediately after the conformance statement.</p>
<section id="conf-statements">
<h4>Conformance statements</h4>
<p>The following list explains the meaning of each
recommended conformance statement.</p>
<dl>
<dt data-localization-id="conformance-aaa"
data-localization-mode="compact">This
publication
exceeds accepted accessibility standards</dt>
<dd data-localization-id="conformance-aaa"
data-localization-mode="descriptive">
<p>The publication contains a conformance
statement that it meets the EPUB
Accessibility and
WCAG 2 Level AAA standard</p>
</dd>
<dt data-localization-id="conformance-aa"
data-localization-mode="compact">This
publication
meets accepted accessibility standards</dt>
<dd data-localization-id="conformance-aa"
data-localization-mode="descriptive">
<p>The publication contains a conformance
statement that it meets the EPUB
Accessibility and
WCAG 2 Level AA standard</p>
</dd>
<dt data-localization-id="conformance-a"
data-localization-mode="compact">This
publication meets
minimum accessibility standards</dt>
<dd data-localization-id="conformance-a"
data-localization-mode="descriptive">
<p>The publication contains a conformance
statement that it meets the EPUB
Accessibility and
WCAG 2 Level A standard</p>
</dd>
<!--To be Confirmed (see https://github.com/w3c/publ-a11y/issues/368)-->
<dt data-localization-id="conformance-no"
data-localization-mode="compact">The publication
does
not include a conformance statement</dt>
<dd data-localization-id="conformance-no"
data-localization-mode="descriptive">
<p>The conformance metadata is missing and
conformity to a standard of this publication
is
unknown</p>
</dd>
<dt>Certifier's name</dt>
<dd>Identifies the organization providing the
certification review or process for
certification. </dd>
<dt>Certifier's Credentials </dt>
<dd>If the certifier has a badge or a credential,
then the text is provided. If there is a link
to their credential, then this can be provided
as a link. If the certifier has a logo or
badge, this can be displayed. The display of the
logo or badge can be arranged between the
certifier and the distributor showing the
accessibility metadata.</dd>
</dl>
</section>
<section id="detailled-conformance-information">
<h4>Detailed conformance information</h4>
<p>The following information can be placed in a section
that shows the details of the conformance
information.</p>
<dl>
<dt>Conformance Statement</dt>
<dd>Identifies the accessibility specification and
the conformance level to which the
publication assertions are made. When the
publication claims to conform to more than one
specification, additional conformance statements
may be provided.</dd>
<dt id="certificate-date">Certification date</dt>
<dd>If the date of the certifier's evaluation is
provided, then this would be of interest. This
is normally associated with the certifier.</dd>
<dt id="certifier-report">Certifier's Report</dt>
<dd>If a link to a report is provided, this may be
of interest.</dd>
</dl>
</section>
<section id="conf-examples">
<h4>Examples</h4>
<p>Four examples are provided for the conformance
statement, one shows a statement that claims to
meet recommended accessibility standards and a
second that claims to meet the minimum level. The
third example shows a publication with unknown
accessibility, and the final one shows that the
conformance information is missing.</p>
<p>The examples present the conformance statement, the
certifier, the certifiers credentials and is
followed by the detailed conformance information
section </p>
<aside class="example"
title="Conformance statement that claims to meet accepted accessibility standards followed by detailed conformance information">
<p data-localization-id="conformance-aa"
data-localization-mode="compact">This
publication meets
accepted accessibility standards</p>
<p>
<span
data-localization-id="conformance-certification-info"
data-localization-mode="compact">The
publication was certified by</span>
Foo's Accessibility Testing
</p>
<p>
<span
data-localization-id="conformance-certifier-credentials-prefix"
data-localization-mode="compact">The certifier 's credential is</span> "Enterprise
Accessibility Rating"
</p>
<p data-localization-id="conformance-details">
Detailed conformance information</p>
<p>
<span
data-localization-id="conformance-claim">This
publication claims to meet</span>
<span
data-localization-id="conformance-epub-accessibility-1-1">EPUB
Accessibility
1.1</span>
<span
data-localization-id="conformance-wcag-2-1"
data-localization-mode="descriptive">Web
Accessibility Content Guidelines (WCAG)
2.1</span>
<span
data-localization-id="conformance-level-aa">Level
AA</span>
</p>
<p><span data-localization-id="conformance-certification-info"
data-localization-mode="descriptive">The
publication was certified on</span>
2021-09-07</p>
<p><span
data-localization-id="conformance-certifier-report">For
more information refer to the
<a
href="http://www.example.com/a11y/report/9780000000001">certifier's
report</a></span>
</p>
</aside>
<aside class="example"
title="Conformance statement that claims to meet minimum accessibility standards followed by detailed conformance information">
<p data-localization-id="conformance-a"
data-localization-mode="compact">This
publication meets
minimum accessibility standards</p>
<p>
<span
data-localization-id="conformance-certification-info"
data-localization-mode="compact">The
publication was certified by</span>
Foo's Accessibility Testing
</p>
<p>
<span
data-localization-id="conformance-certifier-credentials-prefix"
data-localization-mode="compact">The certifier 's credential is</span> "Enterprise
Accessibility Rating"
</p>
<p data-localization-id="conformance-details">
Detailed conformance information</p>
<p>
<span
data-localization-id="conformance-claim">This
publication claims to meet</span>
<span
data-localization-id="conformance-epub-accessibility-1-0">
EPUB Accessibility 1.0 </span>
<span
data-localization-id="conformance-wcag-2-2"
data-localization-mode="descriptive">Web
Content Accessibility Guidelines (WCAG)
2.2</span>
<span
data-localization-id="conformance-level-a">Level
A</span>
</p>
<p><span data-localization-id="conformance-certification-info"
data-localization-mode="descriptive">The