Merge pull request #2946 from w3c/bruce-usab-redundant-entry-privacy

Update redundant-entry.html

understanding/22/redundant-entry.html

@@ -32,8 +32,8 @@ <h2>Redundant Entry Success Criteria text</h2>
      </section>
 
     <section id="intent">
-        <h2>Intent of Redundant Entry</h2>
 
+      <h2>Intent of Redundant Entry</h2>
 
         <p>The intent of this Success Criterion is to ensure that users can successfully navigate multi-step processes. It reduces cognitive effort where  information is asked for more than once during steps in a process. It also reduces the need to recall information provided in a previous  step.</p>
 
@@ -55,6 +55,8 @@ <h2>Intent of Redundant Entry</h2>
 
         <p>This Success Criterion does not impact <a href="accessible-authentication.html">Accessible Authentication</a>, for which allowing auto-filling of passwords is a sufficient technique. In that case the filling is performed by the user's browser. Redundant Entry is asking for the website content to make the previous entry available, but not between sessions or for essential purposes such as asking for a password.</p>
 
+        <p>This criterion does not include requirements or exceptions specific to privacy or personally identifiable information (PII), but when implementing techniques such as auto-population, authors should ensure data protection when storing information even temporarily during a process. It is possible to eliminate redundant entry in ways that do not introduce additional privacy risks, but it is also possible that a poor implementation (for meeting this criterion) could leak additional PII.</p>
+
         <h3>Exceptions</h3>
 
         <p>There are exceptions for:</p>
@@ -88,13 +90,13 @@ <h2>Examples of Redundant Entry</h2>
    </section>
 
    <section id="techniques">
+
       <h2>Techniques for Redundant Entry</h2>
 
-
       <section id="sufficient">
+
          <h3>Sufficient Techniques for Redundant Entry</h3>
 
-
          <ul>
             <li><a href="../../techniques/general/G221">"Provide data from a previous step in a process</a></li>
             <li>Not requesting the same information twice in multiple steps (Potential future technique)</li>