Merge pull request #3131 from w3c/issue2692accessible-authentication

Example section update
w3c · Apr 12, 2023 · 09ec662 · 09ec662
2 parents 27ed793 + 1074f0f
commit 09ec662
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 1 deletion.
diff --git a/understanding/22/accessible-authentication-enhanced.html b/understanding/22/accessible-authentication-enhanced.html
@@ -68,7 +68,7 @@ <h2>Benefits of Accessible Authentication (Enhanced)</h2>
 
    <section id="examples">
       <h2>Examples of Accessible Authentication (Enhanced)</h2>
-      <p>The examples of this success criterion are very similar to the <a href="accessible-authentication.html#examples">Accessible Authentication</a>.</p>
+      <p>The examples of this Success Criterion are the same as the <a href="accessible-authentication.html#examples">Accessible Authentication</a> examples.</p>
       <ul>
         <li>A web site uses a properly marked up username (or email) and password fields as the login authentication (meeting <a href="identify-input-purpose">Success Criterion 1.3.5 Input Purpose</a> and <a href="name-role-value">Success Criterion 4.1.2: Name, Role, Value</a>). The user's browser or integrated third-party password manager extension can identify the purpose of the inputs and automatically fill in the username and password.</li>
         <li>A web site does not block paste functionality. The user is able to use a third-party password manager to store credentials, copy them, and paste them directly into a login form.</li>

diff --git a/understanding/22/accessible-authentication-minimum.html b/understanding/22/accessible-authentication-minimum.html
@@ -138,6 +138,7 @@ <h2>Benefits of Accessible Authentication</h2>
 
    <section id="examples">
       <h2>Examples of Accessible Authentication</h2>
+      <p>The examples of this Success Criterion are the same as the <a href="accessible-authentication-enhanced.html#examples">Accessible Authentication (Enhanced)</a> examples.</p>
 
       <ul>
          <li>A web site uses a properly marked up username (or email) and password fields as the login authentication (meeting <a href="identify-input-purpose">Success Criterion 1.3.5 Input Purpose</a> and <a href="name-role-value">Success Criterion 4.1.2: Name, Role, Value</a>). The user's browser or integrated third-party password manager extension can identify the purpose of the inputs and automatically fill in the username and password.</li>