spec 1 linked patterns checked
MDN input type tel
Documents telephone input semantics, the absence of built-in format validation because phone formats vary globally, custom telephone keyboards on mobile, fallback to text input, and supported attributes including autocomplete, pattern, maxlength, minlength, placeholder, and size.
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 |
|---|---|---|---|
| Phone number entry | Choose phone number entry when the product genuinely needs a telephone route for calls, SMS messages, identity recovery, service contact, delivery coordination, support callbacks, or account verification. | Users can type, paste, autofill, edit, select, undo, and correct the phone value through native input behavior. | MDN supports telephone input semantics, mobile telephone keyboards, fallback to text input, and no automatic global phone-format validation. |
Comparisons supported by this source
- Phone number entry vs text input vs input mask vs inline validation vs error summary
MDN supports telephone input semantics, no built-in global format validation, mobile telephone keyboards, and fallback to text input.
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: .