more caps, clarify

w3c · Jul 6, 2023 · 4dcb70e · 4dcb70e
1 parent 3b77a46
commit 4dcb70e
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/guidelines/index.html b/guidelines/index.html
@@ -636,10 +636,10 @@ <h3>User-generated content</h3>
 			<p>The web content publisher should identify all locations of user-generated content (such as commentary on hosted content, product descriptions for consumer to consumer for sale listings, and restaurant reviews) and perform standard accessibility evaluation analysis for each. If there are no accessibility issues, the user-generated content is fully conforming.</p>
 			<section>
 				<h4>Steps to conform</h4>
-				<p>If accessibility issues are identified, or if the web site author wants to proactively address potential accessibility issues that might arise from user-generated content, then all of the following must be indicated alongside the user-generated content or in an Accessibility Statement published on the web site or product that is linked from the view or page in a consistent location:</p>
+				<p>If accessibility issues are identified, or if the web site author wants to proactively address potential accessibility issues that might arise from user-generated content, then all of the following must be indicated alongside the user-generated content or in an accessibility statement published on the web site or product that is linked from the view or page in a consistent location:</p>
 				<ol>
 					<li>Clearly identify where user-generated content can be found on the publisher’s digital product (perhaps by id href);</li>
-					<li>Clearly identify the steps taken to encourage accessibility in user-generated content such as prompting the user for ALT text for their uploaded images before they are accepted and prohibiting text attributes except as they are part of semantic markup such as strong, headings, etc., as enumerated in Guideline Outcomes;</li>
+					<li>Clearly identify the steps taken to encourage accessibility in user-generated content such as prompting the user for alternative text for their uploaded images before they are accepted and prohibiting text attributes except as they are part of semantic markup such as strong, headings, etc.;</li>
 				</ol>
 			</section>
 					</section>