GOV.UK Design System Names pattern
Documents asking for names only when needed, using Full name for single fields, choosing single or multiple fields based on service need, supporting long names and all needed characters, using autocomplete name or given-name and family-name, disabling spellcheck, avoiding title fields, allowing name changes, and showing specific errors.
What this source can teach
Use this source to compare a documented solution with the task and states in your own product.
- 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 |
|---|---|---|---|
| Name entry | Choose name entry when the product must capture a person's name for identification, correspondence, display, official records, booking, payment, verification, support, or relationship handling. | Users can type, paste, autofill, edit, select, undo, and correct names through native text behavior. | GOV.UK supports needed-only name collection, full-name labels, split-field choice, long and broad character support, common or official-name wording, autocomplete tokens, spellcheck false, title avoidance, name changes, and specific errors. |
Comparisons supported by this source
- Name entry vs text input vs autocomplete vs select vs inline validation vs error summary
GOV.UK supports needed-only name collection, full-name labels, careful split-field choice, long and broad character support, autocomplete tokens, spellcheck false, title avoidance, name changes, and specific errors.
Evidence Role
This source is treated as pattern-library evidence. Its value comes from the specific claims and setting described above.
Publisher: GOV.UK Design System. Last checked: .