Quick reference / FAQ

Practical answers for access decisions

Useful starting points, not universal prescriptions. Follow the topic guides when a decision needs more context.

Is accessibility the same as easier difficulty?

No. Access barriers and intended challenge can be changed independently. A toggle that replaces a painful hold need not change enemy behaviour or strategy. Difficulty options may also be important, but do not replace input and information options. Explore challenge and effort.

Where should a small team start?

Map essential tasks from first launch to recovery. Address blockers, add flexible foundations early and use relevant player feedback to prioritise. Settings that cannot be reached before an inaccessible tutorial are not an effective solution. Plan a focused evaluation.

Does platform remapping replace in-game remapping?

Not completely. In-game remapping can understand actions, update prompts and manage context-specific conflicts. Platform tools remain useful, but cannot always change a game’s timing, hold or simultaneous-input requirements. Review input options.

What is the difference between subtitles and captions?

Subtitles generally represent speech. Captions can also communicate relevant non-speech sounds, speaker identity and other information. Prioritise meaning, timing and readability rather than adding an exhaustive list of every decorative sound. Review interface signals.

Is a colour-vision filter enough?

No single filter is enough. Pair colour with shape, labels or patterns and test essential information against changing backgrounds. Targeted marker customisation can be more useful than changing every colour in the scene.

Can a preset cover everyone?

No. Presets are starting points. Expose their effects and allow independent adjustments where possible. Someone may need larger text but no aim assistance, or a hold alternative without any change to combat timing.

How many disabled players should we test with?

There is no universal number. Plan around research questions and variation in relevant experience, then iterate and expand coverage. A small study can reveal important barriers, but cannot justify claiming that every player’s needs have been represented.

Can a checklist certify our game as accessible?

A checklist can support coverage but does not prove that all players can use the game. Test implementation and communicate specific features and limitations. State what a feature does and where it works rather than presenting a broad access guarantee.

Does this site send my contact message?

No. The contact tool prepares plain text locally for copying or downloading. You choose whether to send it using an email application. The tool has no message-submission endpoint and does not save your draft in browser storage.