A hidden remapping entry lets the default layout deter players

What it is

Settings discoverability is whether players can find and understand a configuration entry point at the exact moment they need it. This builds on the previous three entries and is the link in the chain most easily overlooked: no matter how complete the remapping, how thorough the conflict detection, or how cleanly device profiles are separated, if the entry point itself sits buried deep in a menu, only appears after the game has already started, or carries a name players would never think to search for, a player whose default layout simply does not fit them can quit before ever seeing the option — a feature that exists but is never found is functionally the same as a feature that does not exist.

Why it happens

Any accessibility-related feature's real value depends heavily on the specific moment it gets discovered: once an operational barrier has actually occurred, a player's patience and the psychological cost of continuing to try are already running high, and digging through a deep menu at that point is, for many players, already too late. Placing the remapping entry at launch, in the pause menu, and near the point where a player actually encounters a relevant input prompt turns the feeling of "I simply cannot do this" directly into an actionable adjustment; hiding the entry, conversely, does not make the problem go away — it makes the player misattribute the failure to themselves ("I'm just not skilled enough" rather than "this default was never a fit for me") — and a feature that was supposed to help never actually gets used.

Where it stops holding

Accommodating this need should not mean the settings entry pops up aggressively and interrupts everyone — that disrupts the flow of players who are already skilled and need no reconfiguring at all, and not every player needs to complete a full setup the moment they start the game. A better approach is progressive exposure: a visible but non-mandatory entry from the very start, one dismissible, lightweight nudge once the system detects a player's first input difficulty or a run of repeated failures, and a persistent path back to the settings menu at any time — the feature's existence should never depend solely on out-of-game documentation or community guides to tell players about it; it needs to be discoverable inside the game itself.

Applying it

• Provide a clearly located, clearly named "Controls / Key Bindings" entry both on the pre-game screen and in the in-game pause menu, using wording players would actually think to look for, not internal technical jargon.
• When the system detects a player repeatedly failing at the same action, or switching input devices, proactively offer a dismissible shortcut link to the relevant settings, without forcing it open.
• How to check: with testers whose bodily condition or preferences clearly do not fit the default layout, give no hints and have them find and complete a remapping entirely on their own; record how many menu levels they actually had to click through to find the entry, and what proportion reached it before giving up and quitting.

Related

• Same group: W3.04.1 Remapping must cover every actionable key, not only common ones · W3.04.2 Some chord mappings conflict with system shortcuts and need detection · W3.04.3 Controller and keyboard-mouse remaps need independent saving
• Nearby: W5.06 Menus, pause, and saves · W8.04 One-handed and switch-device operation · J Accessibility and inclusion
• Search terms: settings discoverability · accessibility onboarding · control settings · remapping