Merge pull request #2 from mbgower/graphics-contrast-mg

Graphics contrast mg

understanding/21/graphics-contrast.html

@@ -9,20 +9,20 @@ <h1>Understanding Graphics Contrast</h1>
 		<section id="intent">
 			<h2>Intent</h2>
 
-			<p> If a graphic is needed to understand the content or functionality of the webpage then it should be perceivable by people with low vision or other impairments. Low contrast graphics are more difficult to perceive, and may be completely missed by people with a visual impairment.</p>
-
-			<p>This success criteria was added to WCAG 2.1 so that contrast requirements for text in WCAG 2.0's <a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html">1.4.3 Contrast (Minimum)</a> are applied to  graphics and controls when needed.</p>
+
+			<p>The intent of this Success Criterion is to ensure that user interface components and meaningful graphics are distinguishable by people with moderately low vision (who do not use contrast-enhancing assistive technology). The requirements and rationale are similar to those for text in WCAG 2.0's <a href="https://www.w3.org/TR/UNDERSTANDING-WCAG20/visual-audio-contrast-contrast.html">1.4.3 Contrast (Minimum)</a>.</p>
 
-			<p>The success criteria is applied to icons, inputs, buttons and complete graphics when they are needed to be perceived to understand the content or functionality.</p>
+			<p>Low contrast controls are more difficult to perceive, and may be completely missed by people with a visual impairment. Similarly, if a graphic is needed to understand the content or functionality of the webpage then it should be perceivable by people with low vision or other impairments.</p>
 
 
 			<section id="controls">
-				<h3>Visual identifiers</h3>
-				Controls: focus indicators, borders, and visual information used to indicate state for active user interface components;
+				<h3>User Interface Components</h3>
+				For components on the page which users operate, such as buttons and form fields, any visual boundaries must have sufficient contrast with the adjacent background. Likewise, visual effects which indicate states, such as whether a component is selected or focused, must also provide the same contrast [with 
+				not only should each control be : focus indicators, borders, and visual information used to indicate state for active user interface components;
 				<p>Interactive user interface components, form field borders, focus and selection indicators so they can be perceived by people with moderately low vision (who do not use contrast-enhancing assistive technology).</p>
 			</section>
 
-			
+
 
 
 			<section id="graphical-objects">