epubjs
Version:
Render ePub documents in the browser, across many devices
96 lines (93 loc) • 6.63 kB
HTML
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<title>Chapter 2. Building a Better EPUB: Fundamental Accessibility</title>
<link rel="stylesheet" type="text/css" href="css/epub.css" />
<meta name="dat-origPath" value="/html/body/section/section" /><link rel="prev" href="./ch02_12.html" /><link rel="next" href="./ch02_14.html" /></head><body>
<section class="sect2" title="Footnotes" data-origPath="/html/body/section/section/section[14]">
<h3 class="title" id="_footnotes">Footnotes</h3>
<p>Footnotes present another challenge to reading enjoyment. Prior to EPUB 3,
note references could not be easily distinguished from regular hyperlinks,
and the notes themselves were typically marked up using paragraphs and divs,
which impeded the ability to skip through them or past them entirely.</p>
<p>Picture yourself in a position where you might have to skip a note or two
before you can continue reading after every paragraph. And having to
manually listen to each new paragraph to determine if it’s a note or a
continuation of the text. The practice of clumping all notes at the end of a
section is slightly more helpful, but still interferes with the content flow
however you read.</p>
<p>The <code class="literal">epub:type</code> attribute helps solve both these
problems when used with the new HTML <code class="literal">aside</code>
element, as in the following example:</p>
<pre class="screen"><p>…<a epub:type="noteref" href="#n1">1</a> …</p>
<aside epub:type="footnote" id="n1">
…
</aside></pre>
<p>The “noteref” term in the <code class="literal">epub:type</code> attribute
identifies that the link points to a note, which allows a reading system to
alert the reader they’ve encountered a footnote reference. It also provides
the reader the ability to tell the reading system to ignore all such links
if she wants to read the text through uninterrupted. Don’t underestimate the
irritation factor of constant note links being announced!</p>
<p>Likewise, the <code class="literal">aside</code> element has also been
identified as a footnote, permitting the reading system to skip it if the
reader has chosen to turn off footnote playback. Putting the note in an
<code class="literal">aside</code> also indicates that the content is
not part of the main document flow.</p>
<p>But footnotes are often a nuisance for all readers; sighted readers typically
care just as little to encounter them in the text. Identifying all your
notes could also allow sighted readers to automatically hide them if they
prefer them to not be rendered, saving sometimes limited screen space for
the narrative prose. A configurable reading system that lets you decide what
content you want to see is within reach with semantically meaningful
data.</p></section>
<section class="sect2" title="Page Numbering" data-origPath="/html/body/section/section/section[15]">
<h3 class="title" id="_page_numbering">Page Numbering</h3>
<p>It might seem odd to talk about page numbering in a digital format guide, but
ebooks have been used by students the world over for more than a decade to
facilitate their learning in a world only just weaning itself off print.
Picture yourself using an ebook in a classroom where print books are still
used. When the professor instructs everyone to open their book to a specific
page, your ebook will be most unhelpful if you can’t find the same location.
Or think about trying to quote a passage from a novel in your final paper
and not being able to indicate where in the print source it came from. Page
numbers are not an antiquated concept quite yet.</p>
<p>The practice to date has been to include page numbers using anchor tags, as
in the following example:</p>
<pre class="screen"><a name="page361"/></pre>
<p>But unless a reading system does a heuristic inspection of the <code class="literal">name</code> attribute’s value to see if it starts with
“page” or “pg” or “p” there’s not going to be a lot of value to this kind of
tagging for readers. These kinds of anchor points did give a location for
navigating from the NCX page list, and it did keep the number from being
rendered, but it’s also lost data.</p>
<p>EPUB 3 once again calls on the <code class="literal">epub:type</code>
attribute to include better semantics:</p>
<pre class="screen"><span id="page361" epub:type="pagenumber">361</span></pre>
<p>It’s now clearly stated what the span contains, and the page number no longer
has to be extracted from an attribute and separated from a page identifier
label. It’s now up to the reader and their reading system to determine when
and how to render this information, if at all.</p>
<p>One note when you do include page numbering is to remember that you should
also include the ISBN of the source it came from in the package
metadata:</p>
<pre class="screen"><dc:source>urn:isbn:9780375704024</dc:source></pre>
<p>Inclusion of the ISBN is recommended as it can be used to distinguish between
hardcover and softcover versions, and between different editions, of the
source book. All of these typically would have different pagination, which
would affect the ability of the reader to accurately synchronize with the
print source in use.</p>
<p>This will ensure that students, teachers, professors, and other interested
parties can verify whether the digital edition matches the course criteria.
Of course, the ideal day coming will be when everyone is using digital
editions and sharing bookmarks—and maybe even auto-synchronizing with the
professor’s edition.</p>
<p>But there are also other settings beyond educational where page number can be
useful, too. Reading is also a social activity, and being able to reference
by page numbers in leisure books allows for easier participation in reading
groups, for example.</p>
<p>The world isn’t completely digital yet, so don’t dismiss out of hand the need
for print-digital referencing when you’re producing both formats for a
book.</p>
</section>
</body>
</html>