diff --git a/UX-Guide-Metadata/draft/principles/index.html b/UX-Guide-Metadata/draft/principles/index.html
index 8d0f4320..ea25e670 100644
--- a/UX-Guide-Metadata/draft/principles/index.html
+++ b/UX-Guide-Metadata/draft/principles/index.html
@@ -264,7 +264,7 @@ <h4>Metadata techniques</h4>
 				<h3>Pre-recorded audio</h3>
 				
 				<div class="note">
-					<p>This key information should be hidden if metadata is missing.</p>
+					<p>This key information can be hidden if metadata is missing.</p>
 				</div>
 
 				<p>Indicates the presence of pre-recorded audio and specifies if this audio is standalone (an
@@ -380,7 +380,7 @@ <h4>Metadata techniques</h4>
 				<h3>Navigation</h3>
 				
 				<div class="note">
-					<p>This key information should be hidden if metadata is missing.</p>
+					<p>This key information can be hidden if metadata is missing.</p>
 				</div>
 
 				<p>Identifies the navigation features included in the publication.</p>
@@ -431,7 +431,7 @@ <h4>Metadata techniques</h4>
 				<h3>Charts, diagrams, and formulas</h3>
 				
 				<div class="note">
-					<p>This key information should be hidden if metadata is missing.</p>
+					<p>This key information can be hidden if metadata is missing.</p>
 				</div>
 
 				<p>Indicates the presence of formulas, graphs, charts, and diagrams within the title and whether these
@@ -481,7 +481,7 @@ <h4>Metadata techniques</h4>
 				<h3>Hazards</h3>
 				
 				<div class="note">
-					<p>This key information should be hidden if metadata is missing.</p>
+					<p>This key information can be hidden if metadata is missing.</p>
 				</div>
 
 				<p>Identifies any potential hazards (e.g., flashing elements, background sounds, and motion simulation)
@@ -694,7 +694,7 @@ <h4>Metadata techniques</h4>
 				<h3>Accessibility summary</h3>
 				
 				<div class="note">
-					<p>This key information should be hidden if metadata is missing.</p>
+					<p>This key information can be hidden if metadata is missing.</p>
 				</div>
 				
 				<p>The accessibility summary was intended (in EPUB Accessibility 1.0) to describes in human-readable
@@ -734,7 +734,7 @@ <h4>Metadata techniques</h4>
 				<h3>Additional accessibility information</h3>
 				
 				<div class="note">
-					<p>This key information should be hidden if metadata is missing.</p>
+					<p>This key information can be hidden if metadata is missing.</p>
 				</div>
 
 				<p>This section lists additional metadata categories that can help users better understand the
@@ -831,28 +831,9 @@ <h2>Discovering accessible content</h2>
 				and filtering issues is out of scope for this document, but this section provides some guidance until
 				further research can be carried out.)</p>
 
-			<p>While every user has different accessibility needs, meeting the Web Content Accessibility Guidelines
-				(WCAG) 2.0 requirements, even at level A, is a baseline that ensures a publication will be widely
-				accessible. Publication providers may therefore wish to create specific search capabilities to permit
-				users to find publications that have declared conformance to WCAG at any level. We suggest the creation
-				of an "Accessible" search filter that only returns publications with metadata that indicates conformance
-				to the user-selected WCAG Level &#8212; A, AA, or AAA.</p>
-
-			<p>Publications with full audio created for mainstream use provide important access for many users with
-				disabilities even though they are not accessible to all. (Note that these publications differ from
-				traditional audiobooks in that the audio accompanies the full or partial text of the publication.)
-				Publication providers may already have search tools aimed at finding traditional audiobooks, since they
-				are popular and common, but even if not, this would be a good addition to the suite of tools for finding
-				accessible publications. Publications with full audio may not pass WCAG requirements, however, because
-				they are targeted at a specific audience rather than broadly accessible. As a result, they would not be
-				found using the <q>Accessible</q> search suggested above.</p>
-
-			<p>Any of the metadata fields discussed in detail below could also be used as a filter &#8212; a
-					<q>Screen-reader accessible</q> search would be valued by screen reader users, and a way to ensure
-				no publications with hazards are downloaded would be valued by those with light-sensitive epilepsy or
-				other hazard-related conditions. But if only a single additional search filter fits best in a site's UI,
-				a tool for finding accessible materials that declare conformance to WCAG 2.0 is the best choice to
-				provide.</p>
+			<div class="issue" data-number="196">
+				<p>We are still doing research on this topic, anyone who would like to contribute ideas or feedback from end users can do so by commenting on issue <a href="https://github.com/w3c/publ-a11y/issues/196">#196</a>.</p>
+			</div>
 		</section>
 
 		<section id="localization">