AUDIT SHEET
Game UI Typography and Icon Audit
Check whether game text and icons read during play and at rest.
Why it matters
Text and icons are where players get most of their information, often while something is happening on screen. A font that looks great in a mockup can become unreadable over gameplay, and an icon that seems obvious to the team can mean something different to players. A structured audit catches these problems with evidence rather than opinion.
Workflow
Create audit rows for text role or icon, screen, viewing conditions, risk, and proposed change. Audit hierarchy, similar glyphs such as 0/O, and states with color removed. Test with the actual background, scale options, and intended viewing distance. Ask players for their interpretation before revealing an icon label.
Worked example
A tiny star reads as Favorite in one screen and Rarity in another. Give Favorite a distinct symbol, use an explicit rarity label, and compare the revised list against mixed rarity tiers and long names.
Try it
Audit a settings screen and one in-play alert. Record three observable failures and capture before and after images at the same scale.
Common mistakes to avoid
Reviewing text only on a design canvas. Using the same icon to mean different things. Relying on thin weights or condensed fonts at small sizes. Ignoring confusable characters in codes and numbers. Testing icons with people who already know what they mean.
Use it in your portfolio
Show an audit row, the before and after images at the same scale, and a quote from a player who misread the original icon. This makes typography and iconography decisions concrete for reviewers.
Keep going
Pair this with the Accessibility Checklist and the Localization Stress Test, or practice on a real brief in the Bi-Monthly Challenges. Want feedback from working game UX/UI designers? Explore the UI Peeps Masterclass.