107
107
< body >
108
108
< section id ="abstract ">
109
109
< p > The accessibility of a publication is useful to know regardless of a person's abilities, as features such
110
- as the ability to make visual adjustments make for a better reading experience for everybody. This
110
+ as the ability to make visual adjustments make for a better reading experience for everybody. These guidelines
111
111
document proposes a shared framework for presenting publication accessibility metadata declarations in a
112
112
user-friendly manner — to offer the information to end users in a way that is easy to understand
113
113
regardless of their technical knowledge and is consistent across different publications and different
@@ -130,22 +130,22 @@ <h2>Introduction</h2>
130
130
accessibility concerns are potential issues consumers have when trying to purchase and ultimately read a
131
131
digital publication in any format.</ p >
132
132
133
- < p > The good news is more and more publishers are creating e-books that are Born Accessible (i.e.,
133
+ < p > The good news is more and more publishers are creating digital publications that are Born Accessible (i.e.,
134
134
accessible from the outset, not fixed later) and getting the accessibility validation or audit done by
135
135
independent organizations.</ p >
136
136
</ section >
137
137
< section id ="general-overview ">
138
138
< h2 > General overview</ h2 >
139
139
140
- < p > This document helps those who wish to render accessibility metadata directly to users understand how to
140
+ < p > These guidelines helps those who wish to render accessibility metadata directly to users understand how to
141
141
represent the accessibility claims inherent in machine-readable accessibility metadata in a
142
142
user-friendly User Interface / User Experience (UI/UX). This document targets implementers such as
143
- bookstores, retailers, distributors etc. Content creators will benefit from reading these Principles and
143
+ bookstores, retailers, distributors etc. Content creators will benefit from reading these guidelines and
144
144
are encouraged to follow < a href ="https://www.w3.org/TR/epub-a11y-11/ "> EPUB Accessibility 1.1
145
145
Conformance and Discoverability Requirements section and its techniques.</ a > </ p >
146
146
147
147
< div class ="note ">
148
- < p > This document presents high-level principles without going into technical issues related to the
148
+ < p > This document presents high-level guidelines without going into technical issues related to the
149
149
different metadata standards in the publishing industry. </ p >
150
150
< p > Therefore, < a href ="#techniques "> techniques are available</ a > that illustrate to developers how to
151
151
retrieve data to show the information outlined in this document.</ p >
@@ -260,7 +260,7 @@ <h3>Why this information is important for accessibility</h3>
260
260
deprecated, an EPUB 3 supports page navigation and better structural semantics; an MP3 format audiobook will be
261
261
less structured than an Audiobook, etc. </ li >
262
262
< li > The protection measure may block assistive technologies such as screen readers. In addition,
263
- many specific e-reading devices such as DAISY readers or Braille notepads are not equipped to read
263
+ many specific eReading devices such as DAISY readers or Braille notepads are not equipped to read
264
264
encrypted files. </ li >
265
265
266
266
< li > The name of the publishing house can highlight the efforts it has made in terms of
0 commit comments