spec 4 linked patterns checked
MDN autocomplete credential tokens
Documents credential-related autocomplete tokens including username, current-password, new-password, and one-time-code for account, sign-in, password change, and additional-factor flows.
Read with a purpose
What this source can teach
Use this source to check a technical or accessibility requirement against its exact wording and scope.
- Start with the original. Open the source and find the guidance or example relevant to your task.
- Trace the connection. Use the claim notes below to see how this site applies the source to specific patterns.
- Check the setting. Compare the source's platform, people, and constraints with your own decision.
Pattern Decisions This Source Supports
| Pattern | Supported decision | Required contract | Claim note |
|---|---|---|---|
| Confirm email | Choose confirm email when the service must prove that the user can access the mailbox for account activation, recovery, sensitive notifications, invitation acceptance, or a verified contact route. | The confirmation page states which email address is pending and why access to that mailbox is required. | MDN documents one-time-code autocomplete for short-lived code entry when a confirmation code is used. |
| Confirm phone | Choose confirm phone when the product must prove that the user can receive a time-limited text-message or voice code at an already captured number. | The confirmation page states why phone access is required, what channel was used, and what phone number is being confirmed when disclosure is safe. | MDN documents one-time-code as an autocomplete token for short-lived code entry. |
| Sign in | Choose sign in when the user needs to start or restore an authenticated session for an existing account. | The sign-in form identifies the protected service or destination before requesting credentials. | MDN documents username, current-password, new-password, and one-time-code autocomplete purposes. |
| Two-factor authentication | Choose two-factor authentication when the user must satisfy an additional factor after a primary credential, SSO return, passkey flow, risk signal, new device, or sensitive action. | The challenge appears only when the server requires additional verification and the protected action remains blocked until success. | MDN documents one-time-code autocomplete for additional-factor code entry. |
Comparisons supported by this source
- Sign in vs account creation vs password input vs session timeout warning
MDN documents username, current-password, new-password, and one-time-code autocomplete purposes.
- Two-factor authentication vs sign in vs login vs password reset
MDN supports one-time-code autocomplete for short-lived additional-factor codes.
Evidence Role
This source is treated as spec evidence. Its value comes from the specific claims and setting described above.
Publisher: MDN Web Docs. Last checked: .