service-manual 1 linked patterns checked
ONS Design System Phone numbers pattern
Documents making the needed phone-number type clear, explaining why and when the user may be contacted, allowing familiar phone-number formats, helping users enter the correct format, and showing missing or incorrect details above the field.
Read with a purpose
What this source can teach
Use this source to study a complete public-service task and the guidance that supports its implementation.
- 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. | ONS supports clear phone-number type, why and when contact may happen, familiar formats, format help, and field-level errors. |
Comparisons supported by this source
- Phone number entry vs text input vs input mask vs inline validation vs error summary
ONS supports clear phone-number type, purpose and contact timing, familiar formats, and missing or incorrect error details above the field.
Evidence Role
This source is treated as service-manual evidence. Its value comes from the specific claims and setting described above.
Publisher: Office for National Statistics. Last checked: .