W3C Personal names around the world
Explains global differences in personal-name structure, order, length, scripts, patronymics, multiple family names, single names, nicknames, titles, previous names, pronunciation, native-script and Latin transcription needs, and the risks of splitting or algorithmically parsing names.
What this source can teach
Use this source to examine the study question, participants, observations, and limits before applying a finding.
- 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 supports global-name variation, native scripts, single names, multiple family names, different order, transcription, preferred address, and caution around splitting or parsing names. |
Comparisons supported by this source
- Name entry vs text input vs autocomplete vs select vs inline validation vs error summary
W3C supports broad global-name variation, single names, multiple family names, different order, native scripts, pronunciation and transcription needs, and caution around splitting or parsing names.
Evidence Role
This source is treated as ux-research evidence. Its value comes from the specific claims and setting described above.
Publisher: W3C Internationalization. Last checked: .