Skip to content

Commit 4f86765

Browse files
committed
Merge branch 'Note-Compact-vs-Descriptive' of https://github.com/w3c/publ-a11y into Note-Compact-vs-Descriptive
2 parents 897b736 + f6d643a commit 4f86765

File tree

2 files changed

+43
-6
lines changed

2 files changed

+43
-6
lines changed

a11y-meta-display-guide/2.0/draft/techniques/epub-metadata/index.html

+15-6
Original file line numberDiff line numberDiff line change
@@ -85,17 +85,26 @@ <h2>EPUB Accessibility Metadata</h2>
8585

8686
<aside class="example" title="Compact Versus Descriptive">
8787
<pre>
88-
<code>data-localization-id="visual-adjustments-modifiable" data-localization-mode="compact"</code> "Appearance can be modified"
89-
90-
Versus
91-
<code>data-localization-id="visual-adjustments-modifiable" data-localization-mode="descriptive"</code> "Appearance of the text and page layout can be modified according to the capabilities of
92-
the reading system (font family and font size, spaces between paragraphs, sentences,
93-
words, and letters, as well as color of background and text)."
88+
<code>
89+
"visual-adjustments":
90+
{
91+
"visual-adjustments-title": "Visual adjustments",
92+
"visual-adjustments-modifiable":
93+
{
94+
"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)",
95+
"compact": "Appearance can be modified"
96+
}
97+
}
98+
</code>
9499
</pre>
95100
</aside>
96101

97102
The option is yours to provide either the "compact" or "descriptive" versions to the end user or perhaps even allow the user to choose what they wish to see.
98103

104+
<aside class="ednote">
105+
Link to the English JSON file where this example is taken from.
106+
</aside>
107+
99108
</aside>
100109

101110

a11y-meta-display-guide/2.0/draft/techniques/onix-metadata/index.html

+28
Original file line numberDiff line numberDiff line change
@@ -88,6 +88,34 @@ <h2>ONIX Metadata</h2>
8888
This document provides techniques for meeting the guidelines of the <a href="../../guidelines/">User Experience Guide for Displaying Accessibility Metadata</a>. It provides practical examples for extracting information from the ONIX metadata for showing it to the end users.
8989
</p>
9090

91+
<aside class="note">
92+
The examples provided in this document demonstrate the "compact" version of what is to be displayed.
93+
For every text string both the "compact" or the "descriptive" options are available.
94+
95+
<aside class="example" title="Compact Versus Descriptive">
96+
<pre>
97+
<code>
98+
"visual-adjustments":
99+
{
100+
"visual-adjustments-title": "Visual adjustments",
101+
"visual-adjustments-modifiable":
102+
{
103+
"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)",
104+
"compact": "Appearance can be modified"
105+
}
106+
}
107+
</code>
108+
</pre>
109+
</aside>
110+
111+
The option is yours to provide either the "compact" or "descriptive" versions to the end user or perhaps even allow the user to choose what they wish to see.
112+
113+
<aside class="ednote">
114+
Link to the English JSON file where this example is taken from.
115+
</aside>
116+
117+
</aside>
118+
91119
<p class="note">
92120
ONIX messages describe products for the global book supply chain and will be sent from publisher or creator of the EPUB or digital books with full audio to those who will make the products available for sale, lending or subscription.
93121
These platforms may not yet have the actual files, as they may not yet be ready, or may only choose to list them for sale if they have certain accessibility features.

0 commit comments

Comments
 (0)