epubjs
Version:
Render ePub documents in the browser, across many devices
79 lines (77 loc) • 5.58 kB
HTML
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<title>The Untold Story: Metadata</title>
<link rel="stylesheet" type="text/css" href="css/epub.css" />
<meta name="dat-origPath" value="/html/body/section" /><link rel="prev" href="./ch02s03_0.html" /><link rel="next" href="./ch02s03_2.html" /></head><body>
<ul class="itemizedlist" data-origPath="/html/body/section/ul[1]">
<li class="listitem"><p> No reading system accessibility options disabled (10)
</p></li>
<li class="listitem"><p> Table of contents navigation (11) </p></li>
<li class="listitem"><p> Index navigation (12) </p></li>
<li class="listitem"><p> Reading order (13) </p></li>
<li class="listitem"><p> Short alternative descriptions (14) </p></li>
<li class="listitem"><p> Full alternative descriptions (15) </p></li>
<li class="listitem"><p> Visualised data also available as non-graphical data (16)
</p></li>
<li class="listitem"><p> Accessible math content (17) </p></li>
<li class="listitem"><p> Accessible chem content (18) </p></li>
<li class="listitem"><p> Print-equivalent page numbering (19) </p></li>
<li class="listitem"><p> Synchronised pre-recorded audio (20) </p></li>
</ul>
<p data-origPath="/html/body/section/p[7]">So, for example, if our EPUB contains accessible math formulas (using MathML) we
would indicate it as follows:</p>
<pre class="screen" data-origPath="/html/body/section/pre[2]"><ProductFormFeature>
<ProductFormFeatureType>09</ProductFormFeatureType>
<ProductFormFeatureValue>17</ProductFormFeatureValue>
</ProductFormFeature></pre>
<p data-origPath="/html/body/section/p[8]">Likewise, to indicate accessible chemistry content (using ChemML) we would use the
value <code class="literal">18</code>:</p>
<pre class="screen" data-origPath="/html/body/section/pre[3]"><ProductFormFeature>
<ProductFormFeatureType>09</ProductFormFeatureType>
<ProductFormFeatureValue>18</ProductFormFeatureValue>
</ProductFormFeature></pre>
<p data-origPath="/html/body/section/p[9]">You must repeat the <code class="literal">ProductFormFeature</code> element for each
accessibility requirement your EPUB meets; it is not valid to combine all your
features into a single element.</p>
<p data-origPath="/html/body/section/p[10]">You must also ensure that you make yourself familiar with the requirements for
compliance before adding any accessibility properties; each of the properties
defined in codelist 196 includes conformance criteria. EPUB requires table of
contents navigation, for example, but the addition of the required navigation
document does not automatically indicate compliance. You need to include full
navigation, plus navigation to any tables and figures, before you comply with the
table of contents navigation requirement. Likewise, all EPUBs have a reading order
defined by the spine element in the package document, but that does not mean you
comply to including a reading order. You need to ensure that sidebars and footnotes
and similar information has been properly marked up so as not to interfere with the
narrative flow, as we went over in the section on the logical reading order.</p>
<p data-origPath="/html/body/section/p[11]">It is additionally worth noting that there are three properties that aren’t directly
related to the content of your EPUB:</p>
<ul class="itemizedlist" data-origPath="/html/body/section/ul[2]">
<li class="listitem"><p> Compatibility tested (97) </p></li>
<li class="listitem"><p> Trusted intermediary contact (98) </p></li>
<li class="listitem"><p> Publisher contact for further accessibility information
(99) </p></li>
</ul>
<p data-origPath="/html/body/section/p[12]">Each of these properties requires the addition of a child <code class="literal">ProductFormFeatureDescription</code> element to describe compliance:</p>
<pre class="screen" data-origPath="/html/body/section/pre[4]"><ProductFormFeature>
<ProductFormFeatureType>09</ProductFormFeatureType>
<ProductFormFeatureValue>97</ProductFormFeatureValue>
<ProductFormFeatureDescription>
Content has been tested to work on iBooks, Sony Reader and Adobe Digital
Editions in both scripting enabled and disabled modes.
</ProductFormFeatureDescription>
</ProductFormFeature></pre>
<p data-origPath="/html/body/section/p[13]">Whatever compatibility testing you’ve performed should be listed using code 97 so
that readers can better determine the suitability of your ebook for their purposes.
Not all reading systems and assistive technologies work alike, or interact well
together, and real-world testing is the only way to tell what does and does not
work.</p>
<p data-origPath="/html/body/section/p[14]">There are organizations who specialize in testing across a broad spectrum of devices
who can assist you in evaluating your content, as this kind of evaluation can be no
small undertaking. A good practice to develop, for example, might be to periodically
have typical examples of content coming out of your production stream tested for
compatibility issues. The resulting statement could then be re-used across much of
your content, so long as the features and markup used remain consistent.</p>
</body>
</html>