Skip to content
This repository has been archived by the owner on May 10, 2018. It is now read-only.

Commit

Permalink
updated xhtml pages;
Browse files Browse the repository at this point in the history
update nav pages;
add last update dates
  • Loading branch information
mattgarrish committed Aug 9, 2016
1 parent 5da75d6 commit 80279a0
Show file tree
Hide file tree
Showing 67 changed files with 395 additions and 656 deletions.
1 change: 1 addition & 0 deletions guidelines/content/about.html
Expand Up @@ -39,6 +39,7 @@ <h2>About this Guide</h2>
</section>
</section>
<footer>
<p>This page last updated August 5, 2016.</p>
<p>Please ask questions about these guidelines in the <a href="http://idpf.org/forums">IDPF forums</a>.<br/>To report
typos, errors and omissions, please open an issue in the <a
href="https://github.com/IDPF/a11y-guidelines/issues">github tracker</a>.</p>
Expand Down
1 change: 1 addition & 0 deletions guidelines/content/conformance/s508.html
Expand Up @@ -491,6 +491,7 @@ <h3>Additional Resources</h3>
</section>
</section>
<footer>
<p>This page last updated August 5, 2016.</p>
<p>Please ask questions about these guidelines in the <a href="http://idpf.org/forums">IDPF forums</a>.<br/>To report
typos, errors and omissions, please open an issue in the <a
href="https://github.com/IDPF/a11y-guidelines/issues">github tracker</a>.</p>
Expand Down
1 change: 1 addition & 0 deletions guidelines/content/fixed/img.html
Expand Up @@ -78,6 +78,7 @@ <h3>Compliance References and Standards</h3>
</section>
</section>
<footer>
<p>This page last updated August 5, 2016.</p>
<p>Please ask questions about these guidelines in the <a href="http://idpf.org/forums">IDPF forums</a>.<br/>To report
typos, errors and omissions, please open an issue in the <a
href="https://github.com/IDPF/a11y-guidelines/issues">github tracker</a>.</p>
Expand Down
1 change: 1 addition & 0 deletions guidelines/content/fixed/xhtml.html
Expand Up @@ -89,6 +89,7 @@ <h3>Compliance References and Standards</h3>
</section>
</section>
<footer>
<p>This page last updated August 5, 2016.</p>
<p>Please ask questions about these guidelines in the <a href="http://idpf.org/forums">IDPF forums</a>.<br/>To report
typos, errors and omissions, please open an issue in the <a
href="https://github.com/IDPF/a11y-guidelines/issues">github tracker</a>.</p>
Expand Down
1 change: 1 addition & 0 deletions guidelines/content/glossary.html
Expand Up @@ -299,6 +299,7 @@ <h3>X</h3>
</section>
</section>
<footer>
<p>This page last updated August 5, 2016.</p>
<p>Please ask questions about these guidelines in the <a href="http://idpf.org/forums">IDPF forums</a>.<br/>To report
typos, errors and omissions, please open an issue in the <a
href="https://github.com/IDPF/a11y-guidelines/issues">github tracker</a>.</p>
Expand Down
1 change: 1 addition & 0 deletions guidelines/content/mathml/desc.html
Expand Up @@ -160,6 +160,7 @@ <h3>Frequently Asked Questions</h3>
</section>
</section>
<footer>
<p>This page last updated August 5, 2016.</p>
<p>Please ask questions about these guidelines in the <a href="http://idpf.org/forums">IDPF forums</a>.<br/>To report
typos, errors and omissions, please open an issue in the <a
href="https://github.com/IDPF/a11y-guidelines/issues">github tracker</a>.</p>
Expand Down
1 change: 1 addition & 0 deletions guidelines/content/meta/onix.html
Expand Up @@ -374,6 +374,7 @@ <h3>Frequently Asked Questions</h3>
</section>
</section>
<footer>
<p>This page last updated August 5, 2016.</p>
<p>Please ask questions about these guidelines in the <a href="http://idpf.org/forums">IDPF forums</a>.<br/>To report
typos, errors and omissions, please open an issue in the <a
href="https://github.com/IDPF/a11y-guidelines/issues">github tracker</a>.</p>
Expand Down
1 change: 1 addition & 0 deletions guidelines/content/meta/schema.org.html
Expand Up @@ -253,6 +253,7 @@ <h3>Additional Resources</h3>
</section>
</section>
<footer>
<p>This page last updated August 5, 2016.</p>
<p>Please ask questions about these guidelines in the <a href="http://idpf.org/forums">IDPF forums</a>.<br/>To report
typos, errors and omissions, please open an issue in the <a
href="https://github.com/IDPF/a11y-guidelines/issues">github tracker</a>.</p>
Expand Down
16 changes: 4 additions & 12 deletions guidelines/content/nav/landmarks.html
Expand Up @@ -44,22 +44,13 @@ <h2>Landmarks</h2>
(<code>a</code>). Common landmark properties from the <a href="http://idpf.org/epub/vocab/structure/"
>EPUB 3 Structural Semantics Vocabulary</a> include the following:</p>

<ul class="multicol">
<li>cover</li>
<li>titlepage</li>
<li>frontmatter</li>
<ul>
<li>bodymatter</li>
<li>backmatter</li>
<li>toc</li>
<li>loi (list of illustrations)</li>
<li>lot (list of tables)</li>
<li>preface</li>
<li>bibliography</li>
<li>index</li>
<li>glossary</li>
<li>acknowledgments</li>
</ul>
<br />

<p>Unlike the <a href="toc.html"><code>toc nav</code></a>, the <code>landmarks nav</code> must only be a
single flat listing of links.</p>
Expand Down Expand Up @@ -150,8 +141,9 @@ <h3>Frequently Asked Questions</h3>
</section>
</section>
<footer>
<p>Please ask questions about these guidelines in the <a href="http://idpf.org/forums">IDPF forums</a>.<br/>To report
typos, errors and omissions, please open an issue in the <a
<p>This page last updated August 8, 2016.</p>
<p>Please ask questions about these guidelines in the <a href="http://idpf.org/forums">IDPF forums</a>.<br />To
report typos, errors and omissions, please open an issue in the <a
href="https://github.com/IDPF/a11y-guidelines/issues">github tracker</a>.</p>
<p>For a list of changes to this site, refer to the <a
href="https://github.com/IDPF/a11y-guidelines/commits/master">commit log</a>.</p>
Expand Down
34 changes: 14 additions & 20 deletions guidelines/content/nav/loi.html
Expand Up @@ -36,27 +36,20 @@ <h3>In this section:</h3>
<h2>Lists of Illustrations</h2>

<section id="nav020-desc" class="usage">
<p>To facilitate navigation of the content, publications should include a guide to all the illustrations and
figures they contain. Without these quick links, there is often no easy way for many readers to locate
them again. They instead have to navigate through the content of the book until they reach the
location.</p>
<p>To facilitate navigation of the content, publications should include a guide to all the illustrations they
contain. Without these quick links, there is often no easy way for readers to locate the illustrations
again. They instead have to navigate through the content of the book until they reach the location.</p>

<p>The EPUB navigation document can be used to provide this functionality. A list of illustrations can be
defined in the same manner as the table of contents <a href="toc.html">the <code>toc nav</code></a>, but
using a <code>nav</code> element with an <code>epub:type</code> attribute with the value <code
class="property">loi</code> (see <a href="#nav020-ex01">Example 1</a>). The <code>loi nav</code>
should contain only a single ordered list of entries, with each entry linking to a figure or
illustration.</p>
defined in the same manner as the <a href="toc.html">table of contents</a>, but using a <code>nav</code>
element with an <code>epub:type</code> attribute with the value <code class="property">loi</code> (see <a
href="#nav020-ex01">Example 1</a>). The <code>loi nav</code> should contain only a single ordered
list of entries, with each entry linking to a figure or illustrations.</p>

<p>Note that although this navigation aid is not formally defined in the EPUB specification, navigation
documents were made extensible for this purpose. When creating an <code>loi nav</code>, however, you
should also embed the navigation document as content within the publication. Reading systems that
minimally comply with the specification may not provide specialized access to an <code>loi
nav</code>.</p>

<p>An entry for the list of illustrations should also be included in <a href="landmarks.html">the
<code>landmarks nav</code></a>. If the reading system does not support specialized rendering of
the list, a landmarks entry will enable quick reference to the embedded version.</p>
<p>Note that although this type of navigation aid is not formally defined in the EPUB specification,
navigation documents were made extensible for this purpose. When creating an <code>loi nav</code>, you
should also embed the navigation document as content within the publication as Reading systems may not
provide specialized access to it.</p>
</section>

<section id="nav020-ex" class="example">
Expand Down Expand Up @@ -119,8 +112,9 @@ <h3>Frequently Asked Questions</h3>
</section>
</section>
<footer>
<p>Please ask questions about these guidelines in the <a href="http://idpf.org/forums">IDPF forums</a>.<br/>To report
typos, errors and omissions, please open an issue in the <a
<p>This page last updated August 8, 2016.</p>
<p>Please ask questions about these guidelines in the <a href="http://idpf.org/forums">IDPF forums</a>.<br />To
report typos, errors and omissions, please open an issue in the <a
href="https://github.com/IDPF/a11y-guidelines/issues">github tracker</a>.</p>
<p>For a list of changes to this site, refer to the <a
href="https://github.com/IDPF/a11y-guidelines/commits/master">commit log</a>.</p>
Expand Down
28 changes: 12 additions & 16 deletions guidelines/content/nav/lot.html
Expand Up @@ -37,24 +37,19 @@ <h2>Lists of Tables</h2>

<section id="nav025-desc" class="usage">
<p>To facilitate navigation of the content, publications should include a guide to all the tables they
contain. Without these quick links, there is often no easy way for many readers to locate them again.
They instead have to navigate through the content of the book until they reach the location.</p>
contain. Without these quick links, there is usually no easy way for readers to locate the tables again.
They have to navigate through the content of the book until they reach the location.</p>

<p>The EPUB navigation document can be used to provide this functionality. A list of tables can be defined in
the same manner as the table of contents <a href="toc.html">the <code>toc nav</code></a>, but using a
<code>nav</code> element with an <code>epub:type</code> attribute with the value <code
class="property">lot</code> (see <a href="#nav025-ex01">Example 1</a>). The <code>lot nav</code>
should contain only a single ordered list of entries, with each entry linking to a table.</p>
the same manner as the <a href="toc.html">table of contents</a>, but using a <code>nav</code> element
with an <code>epub:type</code> attribute with the value <code class="property">lot</code> (see <a
href="#nav025-ex01">Example 1</a>). The <code>lot nav</code> should contain only a single ordered
list of entries, with each entry linking to a table.</p>

<p>Note that although this type of navigation aid is not formally defined in the EPUB specification,
navigation documents were made extensible for this purpose. When creating an <code>lot nav</code>,
however, you should also embed the navigation document as content within the publication. Reading systems
that minimally comply with the specification may not provide specialized access to an <code>lot
nav</code>.</p>

<p>An entry for the list of tables should also be included in <a href="landmarks.html">the <code>landmarks
nav</code></a>. If the reading system does not support specialized rendering of the list, a
landmarks entry will enable quick reference to the embedded version.</p>
navigation documents were made extensible for this purpose. When creating an <code>lot nav</code>, you
should also embed the navigation document as content within the publication as Reading systems may not
provide specialized access to it.</p>
</section>

<section id="nav025-ex" class="example">
Expand Down Expand Up @@ -114,8 +109,9 @@ <h3>Frequently Asked Questions</h3>
</section>
</section>
<footer>
<p>Please ask questions about these guidelines in the <a href="http://idpf.org/forums">IDPF forums</a>.<br/>To report
typos, errors and omissions, please open an issue in the <a
<p>This page last updated August 8, 2016.</p>
<p>Please ask questions about these guidelines in the <a href="http://idpf.org/forums">IDPF forums</a>.<br />To
report typos, errors and omissions, please open an issue in the <a
href="https://github.com/IDPF/a11y-guidelines/issues">github tracker</a>.</p>
<p>For a list of changes to this site, refer to the <a
href="https://github.com/IDPF/a11y-guidelines/commits/master">commit log</a>.</p>
Expand Down
14 changes: 8 additions & 6 deletions guidelines/content/nav/pagelist.html
Expand Up @@ -38,11 +38,12 @@ <h3>In this section:</h3>
<h2>Page List</h2>

<section id="nav015-desc" class="usage">
<p>If an EPUB has a print counterpart, or is derived from a print source, the pagination should be retained
and included in the publication for cross-referencing.</p>
<p>If an EPUB publication includes <a href="../xhtml/pagenum.html">page break markers</a> it also requires a
page list &#8212; a special navigation component in the EPUB navigation document that provides links to
all the page break locations.</p>

<p>See the section on <a href="../xhtml/pagenum.html">page numbering</a> for more information on how to embed
page references within a publication.</p>
<p>Reading systems can use this list to provide automatic page jump functionality, or simply expose the list
so that users can manually select the page they wish to go to.</p>
</section>

<section id="nav015-ex" class="example">
Expand Down Expand Up @@ -129,8 +130,9 @@ <h3>Frequently Asked Questions</h3>
</section>
</section>
<footer>
<p>Please ask questions about these guidelines in the <a href="http://idpf.org/forums">IDPF forums</a>.<br/>To report
typos, errors and omissions, please open an issue in the <a
<p>This page last updated August 8, 2016.</p>
<p>Please ask questions about these guidelines in the <a href="http://idpf.org/forums">IDPF forums</a>.<br />To
report typos, errors and omissions, please open an issue in the <a
href="https://github.com/IDPF/a11y-guidelines/issues">github tracker</a>.</p>
<p>For a list of changes to this site, refer to the <a
href="https://github.com/IDPF/a11y-guidelines/commits/master">commit log</a>.</p>
Expand Down

0 comments on commit 80279a0

Please sign in to comment.