Skip to content

Commit

Permalink
Merge pull request #430 from w3c/intro-key-information2
Browse files Browse the repository at this point in the history
Added an introduction to key information
  • Loading branch information
GeorgeKerscher authored Oct 15, 2024
2 parents bd74bdd + 0109f56 commit f0c971f
Showing 1 changed file with 21 additions and 1 deletion.
22 changes: 21 additions & 1 deletion UX-Guide-Metadata/draft/principles/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -244,22 +244,42 @@ <h3>Why this information is important for accessibility</h3>
</section>
<section id="order-of-key-information">
<h2>Key accessibility information</h2>

<!--
<div class="note">
<p>When the content creator does not provide any accessibility metadata for a publication, the three
pieces of key information that should always be present can still be shown (with an indication that
the information is missing): <a href="#visual-adjustments">Visual adjustments</a>, <a href="#supports-nonvisual-reading">Supports nonvisual reading</a>,
and <a href="#conformance-group"
>Conformance</a>.</p>
</div>
-->
<section id="intro-key-info" class="introductory">

<h3>Introduction to key accessibility information</h3>
<p>When focusing on the accessibility of a digital publication, three areas of key information come to mind:</p>
<ul>
<li>People who need to adjust the visual presentation want to know if they can enlarge the text, which is essential for low vision users. People with dyslexia must be able to select the font and adjust the foreground, background, and line length. People with low vision and dyslexia represent the largest percentage of the print-disabled population.</li>
<li>People who use a screen reader need to know if all the content in the title will be accessible to them. When images have text descriptions (alt text), they are assured that they will be not missing out on essential information. Blind users will greatly benefit from this information as well as individuals who use the read aloud feature in Reading Systems.</li>
<li> People who are selecting materials for public institutions such as libraries or schools, need to know if the content conforms to accepted standards.</li>
</ul>
<p>This is why these guidelines recommend that three pieces of key information should always be displayed:</p>
<ol>
<li>Visual adjustments</li>
<li>Supports nonvisual reading</li>
<li>Conformance</li>
</ol>
<p>The other five areas provide details about specific features or shortcomings in publications. It is expected that these other areas of key information will give people what they need to make an informed choice to read a particular title.</p>


<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>
<p>In this document are examples of important metadata that is expected to be in a wide range of publications. However, we do not have examples of all possible features that the metadata can express. The techniques have more values than are shown in the examples.
</p>

</div>
</section>
<section id="visual-adjustments">
<h3 data-localization-id="visual-adjustments-title">Visual adjustments</h3>

Expand Down

0 comments on commit f0c971f

Please sign in to comment.