spec 1 linked patterns checked
MDN WebOTP API
Documents phone-number verification with one-time passwords from specially formatted SMS messages, user-consented OTP retrieval, secure-context requirements, cancellation behavior, and use of autocomplete one-time-code with inputmode numeric for SMS-code fields.
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 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 supports SMS OTP retrieval behavior and one-time-code autocomplete for phone-code confirmation fields. |
Comparisons supported by this source
- Confirm phone vs phone number entry vs confirm email vs two-factor authentication
MDN documents SMS OTP retrieval and one-time-code input behavior for phone-code confirmation fields.
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: .