CHECKLIST

Game UI Accessibility Checklist

Use this checklist to review a game menu or HUD against real player tasks and supported settings.

Why it matters

Accessibility issues affect a lot of players, and many of them come from interface decisions: small text, color-only signals, missing subtitles, or timed inputs with no alternative. Catching these early is far cheaper than retrofitting settings after launch. A checklist tied to real player tasks keeps the review practical and connected to how the game is actually played.

Readability and signals

Check text at the intended viewing distance across bright and busy scenes. Test the largest supported UI scale and a long translated string for clipping. Pair essential color cues with text, shape, or icon. Confirm important audio cues have an appropriate visual or other equivalent.

Input, timing, and subtitles

Complete key tasks with each supported input type. Check visible focus, remapped prompts, and that players can exit dialogs. Review hold, repeat, or timed inputs for alternatives where applicable. Enable subtitles during gameplay and verify speaker clues, legibility, timing, and that critical HUD elements remain visible. Check whether reduced motion settings cover meaningful interface motion.

Track findings

Mark each item Pass, Issue, or Not applicable. Log location, setting, observed barrier, who or what task it affects, owner, and retest result. Example: with UI scale set to maximum, the Apply button in the controls screen scrolls out of reach. Verify it can be reached with a controller after the layout fix.

Common mistakes to avoid

Checking screens in isolation instead of during real tasks. Testing at default settings only. Treating an accessibility option as a fix when it doesn’t cover the barrier. Marking items as Pass without noting the setting or input used. Leaving issues without an owner or retest date, so nobody confirms they were fixed.

Use it in your portfolio

Add an accessibility section to your case study with two or three issues you found, the player each one affected, and the design change you made. This shows reviewers that inclusive design is part of your process rather than an afterthought.

Keep going

Pair this with the Typography and Icon Audit and the Controller Navigation Test Script, or practice on a real brief in the Bi-Monthly Challenges. Want feedback from working game UX/UI designers? Explore the UI Peeps Masterclass.

Copyright 2026