Merge pull request #2486 from w3c/patrickhlauke-issue2483-autofill-wh…

…atwg-reference

Update references to HTML autofill/autocomplete

guidelines/input-purposes.html

@@ -2,7 +2,7 @@
 	<h2>Input Purposes for User Interface Components</h2>
 	<p>This section contains a listing of common <a>user interface component</a> input purposes. The terms below are not keywords that must be used, but instead represent purposes that must be captured in the taxonomy adopted by a webpage. Where applicable, authors mark up controls with the chosen taxonomy to indicate the semantic purpose. This provides the potential for user agents and assistive technologies to apply personalized presentations that can enable more people to understand and use the content.</p>
 
-  <p class="note">The list of input type purposes is based on the control purposes defined in the <a href="https://www.w3.org/TR/html52/sec-forms.html#sec-autofill">HTML 5.2 Autofill field section</a>, but it is important to understand that a different technology may have some or all of the same concepts defined in its specification and only the concepts that are mapped to the meanings below are required.</p>
+  <p class="note">The list of input type purposes is based on the control purposes defined in the <a href="https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#autofill">HTML specification's Autofill section</a>, but it is important to understand that a different technology may have some or all of the same concepts defined in its specification and only the concepts that are mapped to the meanings below are required.</p>
 
   <p>The following input control purposes are intended to relate to the user of the content and pertain only to information related to that individual.</p>
 

techniques/failures/F107.html

@@ -80,10 +80,8 @@ <h2>Related Techniques</h2>
     <section id="resources">
         <h2>Resources</h2>
         <ul>
-            <li>WCAG 2.1 - Input Purposes for User Interface Components: 
-                <a href="https://www.w3.org/TR/WCAG21/#input-purposes">https://www.w3.org/TR/WCAG21/#input-purposes</a></li>
-            <li>The HTML5 <code>autocomplete</code> attribute:
-                <a href="https://www.w3.org/TR/html52/sec-forms.html#sec-autofill">https://www.w3.org/TR/html52/sec-forms.html#sec-autofill</a>
+            <li><a href="https://www.w3.org/TR/WCAG21/#input-purposes">WCAG 2.1 - Input Purposes for User Interface Components</a></li>
+            <li><a href="https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#autofilling-form-controls:-the-autocomplete-attribute">HTML <code>autocomplete</code> attribute</a>
             </li>
         </ul>
     </section>

techniques/html/H98.html

@@ -29,7 +29,7 @@ <h2>Description</h2>
 
 			<p>It's important to note the success criterion <a href="identify-input-purpose">Identify Input Purpose</a> and autocomplete attribute only place requirements on input fields collecting information <em><strong>about the user</strong></em>.</p>
 
-	  <p>For the success criterion, it is assumed that the <code>autocomplete</code> attribute is not used on form fields that do not correspond to an autocomplete field described in the <a href="https://www.w3.org/TR/html52/sec-forms.html#autofilling-form-controls-the-autocomplete-attribute">HTML 5.2 specification</a>. If the <code>autocomplete</code> field is used to describe a "custom" taxonomy, rather than that described in the specification, this rule may produce incorrect results. </p>
+	  <p>For the success criterion, it is assumed that the <code>autocomplete</code> attribute is not used on form fields that do not correspond to an autocomplete field described in the <a href="https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#autofilling-form-controls:-the-autocomplete-attribute">HTML specification</a>. If the <code>autocomplete</code> field is used to describe a "custom" taxonomy, rather than that described in the specification, this rule may produce incorrect results. </p>
 			<section>
 				<h3>Security considerations</h3>
 				<p>Organizations can be concerned about allowing input fields to be automatically filled-in. There is sometimes confusion about how browsers save information and the security implications.</p>