Use the real surface
A name that looks elegant in a heading may disappear in a subtitle. Put the candidate in the smallest actual place it will appear. Include surrounding labels, a realistic background, and the intended font. An isolated screenshot of huge type tells you little about the moment when a player is looking for a doorway.
Review more than length
Check similar letter shapes, punctuation, line breaks, contrast, and the distinction between a title and a button. Keep important information available as text, not only as a color or an icon. A symbol can reinforce “saved,” but a text label makes the action easier to understand and easier to announce with assistive technology.
Read a sentence aloud
Use an arrival announcement, an inventory description, and a line of dialogue. Listen for repeated sounds that make nearby names blur. If you supply a pronunciation note, keep it optional; the story should not require the audience to pass a pronunciation exam before it becomes understandable.
Check interruption and return
Step away briefly, then return to the scene without your notes. Which name can you retrieve, and which one requires reopening a character sheet? This is a useful personal exercise, not a controlled user study. If other people participate, record what you actually observed instead of claiming the name has been scientifically validated.
Fix the smallest problem first
Sometimes the name is fine and the introduction is weak. Add a role label, give two similar names different opening sounds, or shorten a map display form. Avoid rewriting the entire naming system to solve a single cramped tooltip. Keep the full form in a codex if the world needs it.
Document the surface
Record where a name was checked, the font and approximate size, and any unresolved issues. This makes later visual changes easier to review. When a new typeface, translation, or layout arrives, repeat the relevant surface check rather than assuming the earlier result still applies.
Choose an actual retrieval task
Instead of asking whether a screen looks attractive, ask someone to find a particular destination or identify which character made a request. Make the task depend on the same information the final interface provides. A map label that is recognizable only after you explain the lore has not yet solved the navigation problem. Observe what the participant tries, which two names they confuse, and whether the surrounding layout contributes. Keep the account proportionate: a small informal exercise can reveal a specific issue, but it does not justify claiming a statistically validated design or universal accessibility. The next revision should address the observed obstacle.
Inspect the set at the same moment
Place the relevant names together at realistic size. A character introduced in another chapter may not compete with the present cast, while two nearly identical inventory names can compete on every turn. Compare openings, word length, visual rhythm, and the ordinary object or role labels beside them. A shared prefix may be a useful family cue, but if it hides the distinction the task requires, change or supplement it deliberately. Do not rely solely on a portrait, hover state, or color. Important distinctions should remain available in text and survive the input method and display conditions your project actually supports.
Keep a chosen short form distinct from clipping
A deliberate short form preserves the identity you want the audience to retrieve. A string cut off by an interface may remove exactly the word that distinguishes it. Decide the short form editorially and record it with the full one. Then check the actual component’s wrapping, truncation, and accessible label. A long title may be appropriate in an inspection panel but awkward in a quick selection list. The solution can be a plain type line and a concise personal title, rather than shrinking the font until every entry technically fits while becoming harder to read.
Use visible counts as a starting measurement
Character count and longest letter group can flag a candidate for closer inspection, especially when a name must fit a narrow label. They do not measure rendered width, pronunciation, reading difficulty, cultural fit, or reader memory. Different letters and fonts occupy different space. A joined compound may have fewer spaces while still creating a difficult uninterrupted group. The studio exposes those counts so you can compare them with your actual layout. Treat the sound preference similarly: it changes candidate ordering by spelling patterns and provides material to read aloud, not an automated professional assessment of how everybody will hear a name.
Review keyboard and focus behavior around results
A naming page is itself an interface. You should be able to reach labeled controls, generate a batch, identify the updated results heading, open the explanation, and save a draft without guessing what an unlabeled icon does. Status messages should report when constraints produce fewer names or storage is unavailable. Those behaviors support a clear editing workflow. They do not establish that the whole site has passed an independent accessibility audit. If a reader reports a barrier, ask for the page and action involved, then fix the specific problem and check the affected path again instead of claiming a broad certification from a single successful interaction.
Write the result of the review
A useful note might say: “In the map view, two harbor names share their only visible opening. We will rename the smaller landing and retain the old label as a linked local alias. The current font and panel width were checked at the smallest supported layout; translated versions still need review.” This identifies the problem, decision, and remaining work. It also distinguishes naming from layout: if a label fails only because the panel is unnecessarily narrow, the interface may need a change. Keep evidence in the order needed by the next contributor rather than a long list of every test action you performed.
Make the next draft your own.
Try the method in a tool, keep a candidate in your notebook, and revise it against your actual project.
A correction or a question about this piece? Contact Drafitlem.