Skip to content

Commit

Permalink
Merge pull request #413 from w3c/pri-title
Browse files Browse the repository at this point in the history
changed title to Accessibility Metadata Display Guide for ...
  • Loading branch information
GeorgeKerscher authored Oct 7, 2024
2 parents 86e6eda + b20d248 commit 11cfe12
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions UX-Guide-Metadata/draft/principles/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,7 @@

<head>
<meta charset="utf-8" />
<title>User Experience Guide for Displaying Accessibility Metadata 2.0</title>
<title>Accessibility Metadata Display Guide for Digital Publications 2.0</title>
<script src="https://www.w3.org/Tools/respec/respec-w3c" class="remove" defer="defer"></script>
<script class="remove">
// <![CDATA[
Expand Down Expand Up @@ -185,7 +185,7 @@ <h2>Publisher metadata ecosystem</h2>
<p>
From here both flow down into the "Metadata Processing" layer where the EPUB metadata gets processed through the "Display Techniques for EPUB Accessibility Metadata", and the "ONIX accessibility metadata" is processed through the "Display Techniques for ONIX Accessibility Metadata."</p>
<p>
Finally from the "Metadata Processing" layer both the Display Techniques for EPUB and ONIX flow into the "Resulting Statements" layer "User Experience Guide for Displaying Accessibility Metadata"</p>
Finally from the "Metadata Processing" layer both the Display Techniques for EPUB and ONIX flow into the "Resulting Statements" layer "Accessibility Metadata Display Guide for Digital Publications"</p>
</details>

</section>
Expand Down Expand Up @@ -213,7 +213,7 @@ <h3>Metadata techniques</h3>
</section>
<section id="general-info">
<h2>General information</h2>
<p>To solve the problem of displaying the accessibility metadata in a human readable form, vendors will determine their correct statement to display (from the User Experience Guide) by parsing the metadata and using the appropriate Display Techniques document. </p>
<p>To solve the problem of displaying the accessibility metadata in a human readable form, vendors will determine their correct statement to display (from the Accessibility Metadata Display Guide for Digital Publications) by parsing the metadata and using the appropriate Display Techniques document. </p>

<p>The product details provide precious information about the usability of the book in relation to specific user needs. The following information should always be displayed:</p>

Expand Down

0 comments on commit 11cfe12

Please sign in to comment.