Buried options make players believe the game lacks support

What it is

A feature's existence and its discoverability are independent propositions: a game may implement a colour-blind mode but bury it in a video-settings submenu corner, and for those who need it the feature does not exist—they search, fail, conclude "this game doesn't support it," and keep playing with preventable discomfort or leave. Perceived absence is discoverability failure's final cost: development resources went into the implementation, but the invisible entry makes the feature's benefit zero for its target population—plus the extra frustration of "I looked and found nothing."

Why it happens

Perceived absence works through conclusion extrapolation after search termination. Players' support search has termination conditions—a bounded number of attempts (two or three menus then stop) and a time budget (no one wants ten minutes in settings)—and the conclusion after termination is "doesn't exist." That conclusion is understandable behaviour, not a cognitive error: facing an unfamiliar menu structure, exhaustive search is unreasonable, and concluding from limited search is rational. The consequence chain: the needy player continues playing through barriers believing "the game doesn't support me" (damaged experience), spreads "this game's accessibility is bad" in the community (shaping other seekers' purchase decisions), or abandons the game outright (the developer's feature investment fully wasted). Evaluation propagation amplifies asymmetrically: positive reviews when support is found ("this game even has a colour-blind mode, props") and negative ones when not ("doesn't even have a colour-blind mode") both circulate, while the fact of the feature's existence gets little discussion—discoverability decides which review gets spoken.

Where it stops holding

The burial problem is more than a "promote it to the top level" hierarchy fix—hierarchy is one dimension; full discoverability includes entry location (where to find it), naming comprehension (knowing what it is once found), and need-timing matching (prompted when needed); missing any one still produces misjudgement. Another misjudgement source is misleading naming: the option exists but its name suggests something else ("colour assist mode" read as a "colour filter aesthetic" rather than "colour-vision support")—found but misused or unused. The information ecosystem outside the game also shapes misjudgement: store pages, official docs, and community guides are how players judge "does this support my needs" before purchase; in-game burial plus out-of-game silence lets misjudgement happen pre-purchase—publicising accessibility features is discoverability's external extension. For users who "searched but didn't find," remediation channels include in-settings search (search by symptom) and a community-checkable support list (the official site enumerating every accessibility feature).

Applying it

• Run a discoverability audit of accessibility options: simulate seekers' paths (starting from symptoms toward features), logging whether each path reaches the feature and in how many steps; any feature unreachable within three steps gets its entry moved.
• Maintain an accessibility feature list on the store page and official site (matching the in-game reality), and prepare standard "where is this feature" answers for community support channels.
• Verification: compare each accessibility feature's actual usage rate against the estimated size of its needing population; anomalously low usage is a burial signal. Also monitor community claims of "this game doesn't support X" against actual feature existence, prioritising entry fixes where misjudgement clusters.

Related

• Same group: W8.08.1 Accessibility settings need one centralised hub, not scattered menus · W8.08.2 First launch should surface accessibility options · W8.08.3 Setting names should describe effects, not just jargon
• Nearby: W8.07 Comfort options · J1.01 Accessibility design principles · W8.08 Discoverability of accessibility settings
• Search terms: feature discoverability · accessibility visibility · settings findability · perceived support