Review game accessibility with AI
Turn barriers in a playable action into design changes the team can test, prioritise and record before release.
Review game accessibility with AI by following a real player action from start to finish. The game-accessibility-specialist skill encourages the team to look beyond whether an options menu exists. A player may still be unable to pause a timed interaction, follow an off-screen audio cue or distinguish two items represented only by colour.
Its working documents connect each barrier to an accommodation, an owner and a test. A small game team can use those notes to decide which change to try in the next build and which question needs a session with players using their own setups.
What it does
- Check the physical demands of sustained, simultaneous or repeated inputs.
- Pair an important sound with a visible cue that conveys the same information.
- Review subtitle size, speaker identification and background contrast.
- Check menu navigation using the supported keyboard or controller.
- Prepare a focused playtest with people who encounter the barrier.
Install and use
- Use the official GameForge plugin in Claude Code with a game build, UI captures or an authorised description of the player flow. Get participants’ consent before including their observations.
- Pick a task and ask for the first point where a player could lose control or information. Define an observable test for the proposed accommodation.
- Try the change with the relevant input and settings. Record what worked and what still depends on a personal setup.
FAQ
Source
Made by Cem Ipek, AlterLab Creative Technologies Laboratory. Original skill: game-accessibility-specialist, published on GitHub under the MIT licence.
View on GitHub