Merge pull request #2238 from w3c/327-visible-controls-editorial

Update visible-controls.html

understanding/22/visible-controls.html

@@ -40,7 +40,7 @@ <h2>Intent of Visible Controls</h2>
 
       <p>The intent of this Success Criterion is to ensure that user interface components (controls) can be found easily by people with cognitive disabilities, vision loss, and mobility and motor impairments.</p>
 
-      <p>Some design approaches hide controls and require certain user interactions (such as mouseover) to display them. Where the hidden controls are needed to complete tasks, the difficulty in discovering the controls can leave some users with disabilities without a way to progress.</p>
+      <p>Some design approaches hide controls and require certain user interactions, such as mouseover, to reveal them (both visually and programmatically). Where the hidden controls are needed to complete tasks, the difficulty in discovering the controls can leave some users with disabilities without a way to progress.</p>
 
 			<section>
 
@@ -72,7 +72,7 @@ <h3>Mobility and motor impairments</h3>
 
       <h3>When Needed</h3>
 
-      <p>Information needed to identify controls does not need to be visible all the time. But information needed to identify controls must be visible <i>when the controls are needed</i> without hover interaction or keyboard focus. Controls can be available through a persistent <b><i>visible entry point</i></b>, such as a menu button that opens subitems. In a multi-step process or multi-part form, controls may be hidden in an earlier step or part; however, at the time the user can move the process forward, the information needed to identify the control, which is usually the control itself, must be visible without hover interaction or keyboard focus.</p>
+      <p>Information needed to identify controls does not need to be visible all the time. But information needed to identify controls must be visible without hover interaction or keyboard focus  <i>when the controls are needed</i>. For example, if the control is required to carry out a task or progress through a user process. Controls can be available through a persistent <b><i>visible entry point</i></b>, such as a menu button that opens subitems. In a multi-step process or multi-part form, controls may be hidden in an earlier step or part; however, at the time the user can move the process forward, the information needed to identify the control, which is usually the control itself, must be visible without hover interaction or keyboard focus.</p>
 
       <p>Ideally the information needed to identify controls exist would be visible all the time. Controls can be available through a persistent visible entry point, such as a menu button that opens subitems. There are also several exceptions outlined in the criterion text:</p>
       <ul>
@@ -135,7 +135,7 @@ <h2>Examples of Visible Controls</h2>
     <ul>
       <li><strong>Indication of which fields are editable: </strong>
          In a web editor, once a page is open for editing, all possible fields that can be edited always display a clear visible activation control, such as a pencil icon.</li>
-      <li><strong>Enable user to always show controls hidden until revealed by hover:</strong> In a web editor that reveals hidden editing controls when a user hovers over them, a setting can be changed so that the editing controls are always shown by default, without requiring a hover event.</li>
+      <li><strong>Enable user to set controls as always visible instead of being hidden until revealed by hover:</strong> In a web editor that reveals hidden editing controls when a user hovers over them, a setting can be changed so that the editing controls are always shown by default, without requiring a hover event.</li>
       <li><strong>Visible access to email controls: </strong> When viewing a list of emails the controls needed to delete or forward the email are not visible unless hovered. When an email has been selected for viewing, the same controls are persistently visible.</li>
       </ul>
       <p class="note">Other Success Criteria apply to the requirement for controls being “visible." Visibility is not limited to appearing graphically on the screen, but also includes following a meaningful sequence, not relying on sensory characteristics, and all other requirements under <a href="../../understanding/distinguishable">1.4: Distinguishable</a>.</p>