GUIDE

Accessible First-Time User Experience

How to design the first launch and tutorial so every player can set the game up their way before anything is timed, loud or fast.

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

Time: Half a day to map and mock up
You’ll need: Your boot flow, tutorial script and settings list
You’ll make: An accessible first-launch flow and a tutorial prompt spec
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.

Put accessibility before anything timed or story-critical. Read system settings first, then offer the essentials and presets.

Why it matters

The first-time user experience decides whether a player can get into the game at all. Many games open with a cutscene, a timed prompt or a fast tutorial before the player has found the settings. A player who needs subtitles misses the setup. A player who can’t hold a button fails the first quick-time event. Fixing this costs little, because most of the work is putting screens in the right order.

Settings before the story

Show a short Before you play screen at first launch with the essentials: subtitles, text size, and narration or audio. Default subtitles to on. Ubisoft reported that 95% of Far Cry New Dawn players kept subtitles on when they started on by default. Offer presets for vision, hearing, motor and cognitive needs, and remind players they can change everything later.

Respect what the player already set

Many players configure accessibility at the system level. If the console has a screen reader, larger text or captions turned on, read those settings where the platform allows and match them. The Last of Us Part II turns on its own text-to-speech automatically when the console setting is on and the language is English. That first screen should also be narrated, use large focus states and have no timers.

Teach one thing at a time

During the tutorial, introduce one action at a time and let the player try it. Let text wait for a button press instead of auto-advancing. Save every tip to a Help or Codex menu so players can replay it. Show the button the player actually mapped, for the device they’re using. Never punish players for pausing or opening settings mid-tutorial.

Step by step

  1. Map your current boot flow from launch to the first moment of real control.

  2. Mark every step that’s timed, loud, fast or text-heavy before settings are reachable.

  3. Move a Before you play screen ahead of those steps, with subtitles, text size and narration.

  4. Add presets, and decide which system settings you can read at launch.

  5. Rewrite tutorial prompts so each teaches one action, waits for input and saves to Help.

  6. Playtest the first ten minutes with subtitles on, text at 200% and remapped controls.

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

A first-launch screen: three essentials, presets for each need, clear focus and a reminder that everything can change later.

Go deeper

Onboarding isn’t only the tutorial. Loading screens, the first menu visit and the first time a new system appears all teach the player something. Give each new mechanic the same treatment: a short prompt, practice without pressure, and a way to read it again.

Be careful with unskippable intros. Warn players before flashing sequences, and make sure every cutscene supports subtitles from the very first frame.

Key terms

  • FTUE: First-time user experience: everything a player sees from first launch until they’re playing on their own.

  • Self-paced text: Text that stays on screen until the player chooses to continue.

  • System settings: Accessibility options set at the console or OS level that games can read.

  • Codex: An in-game reference where players can revisit tips and tutorials.

Before you move on

  • Subtitles, text size and audio are reachable before any cutscene.

  • Subtitles default to on.

  • Presets exist and every setting in them can be adjusted.

  • Tutorial text waits for input and is saved for replay.

  • Prompts show the player’s mapped buttons.

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

Four rules for tutorial prompts that work for everyone, including players who remapped their controls.

Interactive lab
Storyboard stepper
Walk the five panels players go through when learning by doing.
01 · Setup. A dry seedling sits in the player’s path.

Common mistakes to avoid

Opening with a cutscene before subtitles can be turned on. Teaching three actions in one prompt. Putting timers on reading. Hard-coding default button glyphs. Hiding settings until after the tutorial ends.

Use it in your portfolio

Show your boot flow before and after, with the barriers you removed marked on it. Add the Before you play mockup and one rewritten tutorial prompt. It shows you think about the whole player journey, not just single screens.

Keep going

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 the Accessible First-Time User Experience, a UI Peeps guide. The first minute decides whether a player can play at all. Before the title screen, show the essentials: subtitles, text size, and audio.

Ubisoft reported that when Far Cry New Dawn launched with subtitles on by default, ninety-five percent of players kept them on. So default to on. Offer presets for vision, hearing, and motor, the way The Last of Us Part Two does, then let players adjust each setting.

Read the console’s settings when you can. If the system has a screen reader or larger text turned on, match it. Make that first menu narrated, with big focus states and no timers.

During the tutorial, teach one action at a time, let players read prompts at their own pace, and let them replay any tip from a menu. Show the button they actually mapped, not the default. Remind players where settings live, and never punish them for opening the menu.

Copyright 2026