spec 2 linked patterns checked
HTML Standard autofill credential and webauthn tokens
Defines username, current-password, one-time-code, and webauthn autofill behavior, including sign-in pages that can offer saved passwords or public key credentials from the same credential field.
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 |
|---|---|---|---|
| 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. | The HTML Standard supports webauthn credential suggestions alongside current-password on sign-in pages. |
| 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. | The HTML Standard supports one-time-code and webauthn autocomplete behavior for authentication flows. |
Comparisons supported by this source
- Sign in vs account creation vs password input vs session timeout warning
The HTML Standard supports current-password plus webauthn credential suggestions on sign-in pages.
Evidence Role
This source is treated as spec evidence. Its value comes from the specific claims and setting described above.
Publisher: WHATWG. Last checked: .