Skip to content

Commit

Permalink
Merge pull request #187 from w3c/ux-guide-general-overview
Browse files Browse the repository at this point in the history
Proposal for general overview
  • Loading branch information
clapierre authored Oct 23, 2023
2 parents 6edc795 + 5b0524e commit 321cf00
Showing 1 changed file with 13 additions and 11 deletions.
24 changes: 13 additions & 11 deletions UX-Guide-Metadata/draft/principles/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -103,7 +103,7 @@
independent organizations.</p>

<p>This document proposes a shared framework for presenting publication accessibility metadata in a
user-friendly manner.</p>
user-friendly manner, so as to offer the information to end users in a way that is easy for them to understand (even to the less technical) and consistent across different publications and different digital catalogs.</p>
</section>
<section id="sotd"></section>
<section id="general-overview">
Expand All @@ -124,16 +124,14 @@ <h2>General overview</h2>
important accessibility information that helps end users find and determine if the publication can meet
their specific accessibility needs.</p>

<p>Most metadata is meant to be machine-readable so that it aids in user search queries such as <q>Find all
digital publications that contain large print, or braille, or that meet a certain level of
accessibility conformance.</q></p>
<p>All accessibility metadata is meant to be machine-readable – apart from the accessibility summary - in this way accessibility metadata can be extracted and displayed uniformly across different publications and localized to different user interface languages.</q></p>

<p>The exception to this rule is the accessibility summary which, if present, describes in human-readable
prose the accessibility features present in the publication as well as any shortcomings, when
applicable. This summary is intended for direct presentation to end users.</p>

<p>Here is an example of what a user-friendly accessibility metadata web page could look like:</p>
<p>The accessibility summary was intended (in EPUB Accessibility 1.0) to describes in human-readable
prose the accessibility features present in the publication as well as any shortcomings.
From EPUB Accessibility version 1.1 the accessibility summary became a human-readable summary of the accessibility that complements, but does not duplicate, the other discoverability metadata.</p>

<p>This document offers guidance on how to aggregate and display metadata to end users; these are not strict guidelines, but suggestions for providing a consistent experience for users through different portals. Different implementers may choose to implement these guidelines a slightly different way, some examples can be seen in the <a href="#implementations">Implementations</a> section of the document.</p>

<section id="techniques">
<h3>Metadata techniques</h3>

Expand All @@ -160,10 +158,14 @@ <h2>General information (supplement the bibliographic information)</h2>
<section id="order-of-key-information">
<h2>Key accessibility information</h2>

{{/* <div class="note">
<div class="note">
<p>When a publisher does not provide any accessibility metadata for a publication, a statement should be
displayed to the user informing them that no information was supplied.</p>
</div> */}}
</div>

<div class="note">
<p>This document does not define the order in which to show the key accessibility information; each implementer can decide the preferred order for showing the accessibility information that follows.</p>
</div>


<section id="supports-nonvisual-reading">
Expand Down

0 comments on commit 321cf00

Please sign in to comment.