Merge pull request #530 from w3c/negative-claims

Filtering and note when no metadata

a11y-meta-display-guide/2.0/draft/guidelines/index.html

@@ -532,7 +532,7 @@ <h3>Introduction to key accessibility information</h3>
 			</ul>
 
 			<p>This is why these guidelines recommend that the following areas
-				of key information should always be
+				of key information should be
 				displayed:</p>
 
 			<ul>
@@ -546,6 +546,7 @@ <h3>Introduction to key accessibility information</h3>
 				expected that these other areas of key information will
 				give people what they need to make an
 				informed choice to read a particular e-book.</p>
+<div class="note"><p>When no accessibility metadata is being provided by the publisher, making a statement that the item is "unknown" or "The metadata was not provided" creates a negative statement, which the publisher did not make. The distributer may not be allowed to show statements the publisher did not make. </p></div>
 
 			<div class="note">
 				<p>This document does not define the order in which to
@@ -566,7 +567,7 @@ <h3 data-localization-id="visual-adjustments-title">Visual
 				adjustments</h3>
 
 			<div class="note">
-				<p>This key information should always be displayed, even
+				<p>This key information should be displayed, even
 					if there is no metadata (See the examples
 					where the metadata is not known). </p>
 			</div>
@@ -667,7 +668,7 @@ <h3 data-localization-id="nonvisual-reading-title">Support
 				for nonvisual reading</h3>
 
 			<div class="note">
-				<p>This key information should always be displayed, even
+				<p>This key information should be displayed, even
 					if there is no metadata (See the examples
 					where the metadata is not known). </p>
 			</div>
@@ -765,7 +766,7 @@ <h3 data-localization-id="conformance-title">Conformance
 			</h3>
 
 			<div class="note">
-				<p>This key information should always be displayed, even
+				<p>This key information should be displayed, even
 					if there is no metadata (See the examples
 					where the metadata is not known). </p>
 			</div>
@@ -1839,7 +1840,7 @@ <h2>Discovering accessible content</h2>
 			determining usability.</p>
 
 		<p>Taking into consideration those realities, the following
-			sections propose a minimum and an extension set
+			sections propose a minimum and an extended set
 			for filtering options. Mostly any specific information could
 			be added if considered of use for the
 			public of the platform.</p>
@@ -1860,11 +1861,12 @@ <h3>Minimum filtering set</h3>
 				around the ways of consuming the content. These are:</p>
 
 			<ol>
+<li>Titles that support visual adjustments</li>
 				<li>Titles that support nonvisual reading</li>
-				<li>Titles that support visual adjustments</li>
 			</ol>
 
 			<p>Of note, only the positive values should be used.</p>
+<div class="note"><p>It is recommended to filter on the original accessibility metadata values. The strings presented to the user for filtering may draw from the user-facing strings.</p></div>
 
 			<aside class="example" title="Minimum filtering options">
 				<ul>
@@ -1878,25 +1880,20 @@ <h3>Minimum filtering set</h3>
 			<h3>Extended filtering set</h3>
 
 			<p> In specific domains, the addition of other options will
-				become important to help users find content
-				that responds to a particular need or scenarios. Each
-				domain case would uniquely drive the selection
+				be important to help users find content
+				that responds to a particular need or scenario. Each
+				domain case would drive the selection
 				of appropriate items. Some examples of these domains
 				(not exclusive) are:</p>
 
 			<ul>
 				<li> In an academic context, the presence of printed
 					page numbers may be crucial to make sure the
-					reader will be able to find or make a reference.
+					reader will be able to find or make a citation.
 				</li>
-				<li> In a technical or scientific context, the
-					information about ways provided to access complex
-					contents like Charts, Diagrams, and Formulas would
-					have a strong importance to know if
-					accessibility markup were present.</li>
+				<li> In a technical or scientific context, information about access rich content like charts, diagrams, figures, graphs, math, and chemical formulas will be important.</li>
 				<li> In markets where compliance to legislation is
-					required, understanding conformity information
-					becomes mandatory. </li>
+					required, understanding conformance information may be mandatory. </li>
 				<li> Platforms dedicated to selling children's books and
 					interactive content may want to allow users
 					to select books with no hazards or inform them about
@@ -1905,11 +1902,10 @@ <h3>Extended filtering set</h3>
 
 			<aside class="example" title="Extended filtering options">
 				<ul>
-					<li>Page list</li>
-					<li>Charts, Diagrams, and Formulas</li>
-					<li>Minimum accessibility standards (A)</li>
-					<li>Accepted accessibility standards (AA)</li>
-					<li>No hazards</li>
+					<li>Go to page</li>
+					<li>Contains charts, diagrams, figures, graphs, math, or chemical formulas</li>
+					<li>This publication meets accepted accessibility standards</li>
+						<li>No hazards</li>
 					<li>Prerecorded audio</li>
 				</ul>
 			</aside>