service-manual 1 linked patterns checked
W3C Internationalization Best Practices for personal names
Documents requirements to avoid assuming given-name and family-name order, avoid automatic part extraction, allow single-letter and single-part names, allow punctuation and spaces, preserve casing, avoid family-name requirements, and provide transcription fields when needed.
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 |
|---|---|---|---|
| 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. | W3C best practices support preserving casing, allowing punctuation and spaces, accepting single-letter and single-part names, avoiding family-name requirements, and adding transcription fields when needed. |
Comparisons supported by this source
- Name entry vs text input vs autocomplete vs select vs inline validation vs error summary
W3C best practices support preserving casing, allowing spaces and punctuation, avoiding family-name requirements, accepting single-letter names, and providing transcription fields when needed.
Evidence Role
This source is treated as service-manual evidence. Its value comes from the specific claims and setting described above.
Publisher: W3C Internationalization. Last checked: .