Removing session scope

Author: alastc

guidelines/sc/22/redundant-entry.html

@@ -5,7 +5,7 @@ <h4>Redundant Entry</h4>
     <p class="conformance-level">A</p>
 	<p class="change">New</p>
 
-    <p>Information previously entered by or provided to the user that is required to be entered again in the same <a>process</a> and in the same user-session is either:</p>
+    <p>Information previously entered by or provided to the user that is required to be entered again in the same <a>process</a> is either:</p>
 
     <ul>
         <li>auto-populated, or</li>

understanding/22/redundant-entry.html

@@ -17,7 +17,7 @@ <h2>Status</h2>
 
         <h2>Redundant Entry Success Criteria text</h2>
         <blockquote>
-            <p>Information previously entered by or provided to the user that is required to be entered again in the same <a>process</a> and in the same user-session is either:</p>
+            <p>Information previously entered by or provided to the user that is required to be entered again in the same <a>process</a> is either:</p>
             <ul>
                 <li>auto-populated, or</li>
                 <li>available for the user to select.</li>
@@ -41,7 +41,7 @@ <h2>Intent of Redundant Entry</h2>
 
         <p>Requiring people to recall information already entered in the previous steps can cause them to give up or enter incorrect information. The autocomplete feature of browsers is not considered sufficient because it is the content (the web site) that needs to provide the stored information for a redundant entry, or avoid asking for the same information again.</p>
 
-        <p>This Success Criterion does not add a requirement to remember information between sessions. A <a>process</a> is defined on the basis of an activity and is not applicable when a user returns after closing a session or navigating away.</p>
+        <p>This Success Criterion does not add a requirement to remember information between sessions. A <a>process</a> is defined on the basis of an activity and is not applicable when a user returns after closing a session or navigating away. However, a process can run across different domains, so if a check-out process includes a 3rd party payment provider, that would be in scope.</p>
 
         <p>This Success Criterion does not apply if data is provide by the user with a different method, such as uploading a resume in a document format.</p>