GUIDE

Accessibility Options That Matter

Which accessibility settings to build first, how to organize them, and how to make the options menu itself easy to use on console and PC.

Watch · 16-second preview
0:00 / 0:22

Time: 2–3 hours for a menu pass
You’ll need: Your current settings list, a controller, a mouse and keyboard
You’ll make: A prioritized accessibility menu map with one fully specced option
Prefer to listen? Watch the narrated walkthrough

Color alone fails for many players. Pair every essential state with text, a number, an icon or a pattern.

Group options by player need and put presets on top. Magenta items are the ones to ship first.

Why it matters

Accessibility settings are often the difference between playing a game and refunding it. The Game Accessibility Guidelines note that the features players ask for most are remappable controls, adjustable text size, color-blind support and subtitles. Those are also some of the cheapest to plan for if you start early. A good options menu is a design problem, not a list of toggles: players need to find the right setting, understand it, and see what it does before they commit.

Group by player need

Sort settings into Vision, Hearing, Motor and Cognitive instead of only Graphics, Audio and Controls. Keep the standard tabs too, but give accessibility its own tab and cross-link settings that live in both places, like subtitles. Put presets at the top so one press turns on a full set. The Last of Us Part II did this with vision, hearing and motor presets, then let players tweak each setting afterward.

Ship first, then expand

Start with remapping for every action, text size and UI scale, subtitles with speaker names and a background, color-safe signals, and separate volume sliders for music, effects, voice and UI. Next add hold-to-toggle and mash-to-hold, reduced motion, camera shake, high contrast and aim assist strength. Advanced options like screen narration, audio description and game speed take more engineering, so plan them early if your audience needs them.

Make every option understandable

Each row needs a plain label, a current value, a one-line description and a live preview. Changing subtitle size should show a subtitle right away. Avoid jargon like “dead zone” without an explanation, and never hide a critical option in a submenu with no hint that it exists. Give every group a reset, and save changes between sessions.

Step by step

  1. List every setting your game has today and tag each one Vision, Hearing, Motor or Cognitive.

  2. Compare the list with the basic tier of the Game Accessibility Guidelines and mark what’s missing.

  3. Sort missing items into Ship first, Next and Advanced based on player impact and build cost.

  4. Sketch the accessibility tab with presets on top and the four groups below.

  5. Spec one option fully: label, values, default, description, preview and where else it appears.

  6. Play through the menu with a controller only, then a mouse only, and fix any dead ends.

A findings tracker. Each issue records the setting used, the barrier observed, who it affects, an owner and a retest.

One option, fully specced: obvious focus, a value that changes in place, a plain description and an instant preview.

Go deeper

Presets are a shortcut, not a replacement. A hearing preset might turn on subtitles, speaker names, direction indicators and visual sound cues together. Players still need to adjust each one, because no two players with the same disability need exactly the same setup.

Once you ship, tell players what you built. The Accessible Games Initiative, run by the Entertainment Software Association, defines 24 standard tags such as clear text, large and clear subtitles, and narrated menus. Xbox now shows these tags on digital store pages, and Steam lets developers list accessibility features that players can filter by.

Key terms

  • Preset: A bundle of recommended settings for one kind of need, applied in one step.

  • Hold-to-toggle: Turning an action that needs a held button into a press-on, press-off switch.

  • Live preview: A sample that updates as the player changes a setting, before they leave the menu.

  • Accessibility tags: Standard labels on store pages that tell players which features a game supports.

Before you move on

  • Every action can be remapped, including menu actions.

  • Text size, subtitles and separate volumes exist and save between sessions.

  • Each option has a description and a live preview.

  • The menu works fully with a controller and with a mouse.

  • Presets exist, and every preset setting can still be adjusted.

Cheat sheet: Game UI accessibility. Six steps and a done-when checklist.

Start with the settings players request most, then expand. Plan advanced features early if your audience needs them.

Interactive lab
Accessibility simulator
Preview a HUD through common vision conditions and UI scales, then mark each check.
Simulate
HP
STAMINA
✕ POISONED
RIO: Hold the gate, I’m almost there!
Under “Red-green CVD” the HP and Stamina chips look the same — only the labels save them. The “✕ POISONED” chip adds a symbol and outline, so it still reads.
Health state readable without color
Text readable at largest UI scale
Subtitles legible on bright scenes
Focus always visible

Common mistakes to avoid

Burying accessibility settings three menus deep. Shipping options with no description or preview. Remapping that ignores menu buttons or still shows the old prompts. Treating a difficulty slider as the only accessibility setting. Forgetting to save settings, so players redo them every session.

Use it in your portfolio

Show your before and after menu map, the priority tiers you chose and why, and one fully specced option with its preview. Hiring managers want to see that you can turn a long guideline list into a plan a team can ship.

Keep going

Pair this with the Game UI Accessibility Checklist and the Game Menu Architecture Map, then read Readable Game Text and Color, Contrast and Color-Blind Modes for the two visual settings players use most.

Narrated walkthrough

A one-minute walkthrough of this guide, voiced with ElevenLabs, with captions built in. Read along with the transcript below.

Transcript

This is Accessibility Options That Matter, a UI Peeps guide. You can’t ship every setting, so start with the ones players ask for most: remappable controls, adjustable text size, subtitles, and color-blind friendly signals.

Group your menu by what players need, not by how your engine is organized: Vision, Hearing, Motor, and Cognitive. Put presets at the top, so a player can turn on a whole set in one move, then fine-tune. Every option needs a live preview. If a player changes subtitle size, show a subtitle right there.

Add hold-to-toggle, timing assists, separate volume sliders, a camera shake switch, and reduced motion. Then make the menu itself accessible: large text, a clear focus state, narration if you can, and a back button that always works.

Finally, tell people. Accessible Games Initiative tags on Xbox, and Steam’s accessibility filters, let players find these features before they buy. In your portfolio, show your menu map and one option with its preview.

Copyright 2026