Suggested wording to address Issue #41 1 (#589)

* Suggested wording to address Issue #41 1 * Changes from the meeting. * Typo Co-authored-by: Alastair Campbell <[email protected]>
w3c · Feb 1, 2022 · a8b4b52 · a8b4b52
1 parent 017392b
commit a8b4b52
Showing 1 changed file with 4 additions and 3 deletions.
diff --git a/requirements/index.html b/requirements/index.html
@@ -24,10 +24,11 @@
 		<section>
 			<h2 id="intro">Introduction</h2>
 			<p>People with disabilities can face problems using online content and applications. Disabilities can be permanent, temporary, or recurring limitations. </p>
-			<p>We need guidelines to: </p>
+			<p>We need guidance that: </p>
 			<ul>
-				<li>identify these barriers encountered by people with disabilities. </li>
-				<li>explain how to solve the problems they pose. </li>
+				<li>identifies the barriers encountered by people with disabilities,</li>
+				<li>explains what causes these barriers and who they impact, and</li>
+				<li>suggests how the problems they pose can be solved.</li>
 			</ul>
 			<p>The Web Content Accessibility Guidelines (WCAG) 2.0 were designed to be technology neutral, and has stayed relevant for over 10 years. The Authoring Tool Accessibility Guidelines (ATAG) 2.0 has been implemented in the open source authoring tool communities (chiefly Wordpress and Drupal) with little known uptake in commercial authoring tools. UAAG 2.0 offers useful guidance to user agent developers and has been implemented on an individual success criterion basis. There is no known user agent that has implemented all of UAAG 2.0. </p>
 			<section>