Game storefronts are good at telling us a release date, file size, genre, and whether a game contains in-app purchases. They have been much less consistent about answering a more personal question: can I actually play this?
For a player who needs large subtitles, remappable controls, narrated menus, reduced motion, or an option to save at any time, that answer can decide whether a purchase is useful or wasted. The industry has spent years treating this information as something to hunt down after watching trailers, reading specialist reviews, and digging through menus. A newer cross-industry effort is trying to put it where it belongs: beside the rest of the product information.
The Accessible Games Initiative provides a shared set of accessibility tags that publishers and storefronts can place on game pages and in digital catalogues. It is an Entertainment Software Association project developed by Electronic Arts, Google, Microsoft, Nintendo, Sony Interactive Entertainment, and Ubisoft. Its stated goal is simple: give players clearer information about the accessibility features in a game before they buy it.
That sounds like a small interface change. It could alter discovery in a much bigger way.
What the accessibility tags describe
An accessibility tag is a defined label for a feature that may remove a barrier to play. The initiative covers areas such as input, gameplay, visual presentation, and audio. Examples reported when the system was announced include large and clear subtitles, difficulty levels, save-anytime support, narrated menus, multiple volume controls, mono sound, and chat speech-to-text or text-to-speech.
The exact wording matters. "Accessible" on its own is nearly useless because players do not all face the same barriers. A game may work well for someone who needs subtitle controls and remain impossible for someone who cannot perform repeated button presses. A list of specific features gives the buyer something concrete to evaluate.
The initiative's own site makes another important distinction: the tags identify features; they do not award a universal seal of approval. Participation is voluntary, games without the tags may still contain accessibility options, and the system can coexist with labels already used by individual storefronts.
Accessibility information works best as product information, not praise.
That framing keeps expectations sane. A tag cannot prove that an implementation is good. "Large subtitles" still leaves questions about contrast, speaker names, background opacity, and whether text scales across every menu. "Difficulty levels" does not explain which parts of the experience can be adjusted. Labels are the beginning of an informed decision, not the end of one.
Why buying a game can involve detective work
When accessibility details are absent, players have to assemble them from scattered evidence. A publisher may post a launch-day accessibility article. A specialist outlet may test the options. Someone may upload a settings screen. Another player may answer a forum question. Each source helps, but the process assumes time, confidence, and a willingness to risk spoilers.
It also assumes the information exists. Smaller games may receive no dedicated accessibility coverage. Store descriptions often use broad promises rather than listing settings. Reviews can spend hundreds of words on frame rates and combat feel without saying whether controls can be remapped or subtitle backgrounds can be changed.
This is where consistent labels earn their keep. They move basic compatibility questions earlier in the buying process. A player can rule a game in or out before paying, downloading, or beginning a refund request.
The benefit reaches beyond players with permanent disabilities. Temporary injuries can make ordinary controls difficult. Fatigue can change how long someone can hold a button or react to a prompt. A person playing quietly at night may rely on captions. Someone using a small screen may need larger text. A player new to action games may need generous timing or adjustable difficulty while learning.
Accessibility is specific, but its usefulness travels.
Discovery gets better when needs become searchable
Most game discovery begins with genre and mood: cozy game, tactical RPG, co-op shooter, short narrative adventure. Accessibility adds another layer of intent. A player may want a role-playing game with narrated menus, a puzzle game that does not depend on colour, or an action game that can be played without holding buttons.
If storefronts expose standardized tags as filters, those needs can become part of ordinary browsing. That is a meaningful shift. Players would no longer have to discover an appealing game first and investigate whether it is playable second. They could begin with games that meet their requirements.
This matters for independent developers too. Big releases can fund polished accessibility pages and attract detailed coverage. A small game with thoughtful controls or excellent caption options may have no reliable way to surface that work. Shared labels can make those features legible without requiring a large marketing campaign.
There is a catch: filters are only useful when the catalogue is well tagged. Voluntary adoption will produce gaps. Different publishers may interpret borderline cases differently. Updates can add or break features after launch. Storefronts therefore need definitions, maintenance, and a way to correct inaccurate listings. A stale tag is worse than no tag because it creates confidence the game may not deserve.
Labels cannot replace accessibility reviews
A checklist answers "what is present?" A good accessibility review asks "how well does it work?"
Consider subtitles. A product label might confirm that large, clear subtitles are available. A review can explain whether they remain readable during bright combat scenes, whether environmental dialogue is captioned, whether speaker names are shown, and whether the text disappears too quickly. The same gap appears with remapping, colour alternatives, camera movement, quick-time events, and audio cues.
Specialist criticism remains essential because accessibility is experienced in context. Can I Play That? publishes reviews that discuss concrete barriers and implementations. Community reports often catch problems that a feature list cannot show, especially when a setting works in the main game but not in a tutorial, menu, or late-game sequence.
The strongest purchase path uses both layers:
- Store tags provide a quick, consistent summary.
- Publisher documentation explains settings in detail.
- Accessibility reviews and player reports test how those settings behave.
That is more work than reading a single badge, but much less work than starting from nothing.
The standard has to stay understandable
Common language is the initiative's best idea. The Game Accessibility Guidelines have supported developers since 2012 with guidance grouped by implementation effort and impairment type. The new consumer-facing labels attack a related problem from the other side: how does a buyer recognize those features in a shop?
For that language to last, each tag needs a stable definition. Publishers need to avoid stretching terms until they become marketing copy. Storefronts need to present the labels where people can find them, not bury them behind several taps. Players also need enough detail to understand what a tag does and does not promise.
A shared vocabulary will not make every game playable for every person. No fixed label set can cover every combination of disability, hardware, genre, and individual preference. It can still remove needless uncertainty.
That is a practical standard to judge the system by: does it help somebody make a better decision before spending money?
What players should check before buying
Even with tags, it is worth checking the settings that affect your own play. Start with the barrier, not with a generic accessibility score.
For visual access, look for text size, contrast, colour alternatives, screen-reader or narrated-menu support, and options that reduce visual clutter. For hearing access, check captions beyond dialogue, speaker identification, directional indicators, and separate volume controls. For motor access, investigate full remapping, hold-versus-toggle choices, repeated-input options, timing windows, and support for alternative controllers. For cognitive access, useful details can include objective reminders, adjustable difficulty, clear navigation cues, pause behaviour, and the freedom to save.
Then ask how widely the feature applies. Does remapping cover menus as well as gameplay? Does text scaling affect inventory screens? Can camera shake be reduced everywhere? Does "save anytime" mean a true manual save, or a checkpoint created outside combat?
These questions are not picky. They are the difference between a listed option and a dependable one.
What better accessibility metadata changes
The immediate gain is fewer bad purchases. The longer-term gain is better feedback.
When accessibility features have consistent names, players can ask for them more precisely. Developers can see which options people search for. Reviewers can compare implementations without inventing a new vocabulary for every release. Storefront teams can identify empty or incomplete listings. The conversation gets less vague.
It may also change how games are recommended between friends. "You would like this" becomes "you would like this, and it has the subtitle and motion settings you need." That second sentence is far more useful.
Perthro is built around recording and sharing what people play. Its current iPhone app lets players track games, rate them, write reviews, make lists, and follow friends. Those reviews can include the practical details that ordinary scores miss. A five-star rating says how someone felt. A note about readable captions or exhausting button holds tells another player whether the game might fit.
Perthro is free on the App Store and requires iOS 17.0 or later. For help with the app, visit /support, and for conversations with other players, visit /community.
A better store page is only the start
The game industry does not lack accessibility knowledge. Developers, disabled players, advocates, and specialist critics have built years of guidance. What has been missing is a dependable bridge between that knowledge and the moment someone considers buying a game.
Accessibility labels can become part of that bridge. Their success will depend on adoption, accurate definitions, honest tagging, and storefront design that makes the information easy to find. They will still need detailed documentation and real-world reviews beside them.
But putting specific accessibility information on the product page fixes one obvious failure: players should not have to buy a game to discover whether they can play it.