spec 4 linked patterns checked
MDN HTML autocomplete password tokens
Documents current-password for an existing password, new-password for account creation or password changes, one-time-code for short-lived codes, and the role of autocomplete values in identifying input purpose.
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 |
|---|---|---|---|
| Account creation | Choose account creation when a persistent account is required for repeated access, saved data, account management, security, authorization, legal accountability, or returning to drafts. | The flow states why the account is needed before asking for credentials. | MDN supports correct new-password autocomplete for account creation fields. |
| Password creation | Choose password creation when the user must choose or replace a reusable password, passphrase, or memorized secret. | Typing, paste, autofill, password-manager generation, deletion, and selection follow native input behavior. | MDN supports new-password for creation and change flows, current-password for existing secrets, and one-time-code for short-lived codes. |
| Password input | Choose password input when the value is a password, passphrase, PIN-like memorized secret, current password, reauthentication secret, or credential confirmation value. | Typing, paste, selection, deletion, undo, and password-manager autofill work through native input behavior. | MDN supports current-password, new-password, and one-time-code autocomplete distinctions. |
| Password reset | Choose password reset when an unauthenticated or partially authenticated user needs to regain account access by proving control of a recovery channel and setting a replacement password. | Submitting an identifier always leads to the same visible confirmation, regardless of whether an account exists. | MDN supports autocomplete new-password semantics for the replacement password step and one-time-code semantics for short reset codes. |
Comparisons supported by this source
- Password creation vs password input vs inline validation vs error summary
MDN supports new-password for account creation and password changes, current-password for existing secrets, and one-time-code for short-lived codes.
- Password input vs text input vs inline validation vs error summary
MDN supports current-password, new-password, and one-time-code autocomplete distinctions.
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: .