Accessibility in Gaming: The State of Play in 2026

Ten years ago, getting a mainstream game to talk to a screen reader usually meant hunting down a volunteer modder. Fans built text-injectors and screen-reader patches, plus mouse-replacement utilities held together with duct tape. Now the big studios publish accessibility trailers and hire leads whose entire job is this stuff. Some even give it a dedicated QA stream. The progress is real. So are the gaps. What follows is my honest read on the industry in 2026: what has genuinely been solved, and where players who don't see a screen the way most people do are still being left behind.

I'm writing from a slightly unusual seat. I built EchoQuest, an audio-first AI RPG where a Game Master narrates every scene aloud, and blind and low-vision players are the people I design for first. I hold my own game to the standards I'd use on anybody else's, and I'll admit it hasn't always met them. So this isn't an attack on the industry. Plenty of the largest studios have made sincere, remarkable progress. It's no victory lap, though.

What's Improved

Subtitle and caption standards have climbed a long way. Most major releases now label who's talking and describe the important non-speech sounds, instead of pasting a bare dialogue transcript on screen. Some go further and tell you which direction a sound is coming from. In other words, captions grew from "the script, on screen" into a genuine second channel of information. The 2020s also turned customisable subtitle styling into a baseline expectation rather than a bonus. Changing the size and the background is normal now, and decent contrast and font options usually come along for the ride.

Colorblind modes show up in nearly every AAA title. Separate profiles for the common types of colour blindness (deuteranopia, protanopia and tritanopia) are standard, and many studios add custom colour swaps and high-contrast modes for low-vision players on top. Remember the red-versus-green health bars in competitive shooters? That problem defined a whole generation of accessibility complaints, and it's largely gone.

Controller remapping is simply expected now. Players with motor disabilities can map any button to any input and adjust timing windows. Many play with single-switch or eye-tracking setups. Hardware moved forward as well, and in lasting ways. Microsoft announced the Xbox Adaptive Controller in May 2018, and Sony's Access controller for PS5 launched worldwide on December 6, 2023 with four 3.5mm ports for plugging in third-party switches and accessories. Console-level support for switch input matters a lot here. Even games without first-class accessibility settings often become playable through remapping at the system level.

Cognitive accessibility options, like simplified interfaces and difficulty presets, have spread widely, and objective markers that nudge you onward are now common. The landmark is still The Last of Us Part II. Before launch, Naughty Dog laid out more than 60 accessibility settings on the PlayStation Blog, spanning vision, hearing, motor and cognitive needs. That list included text-to-speech for on-screen text and extra audio cues for traversal and combat. Then Forza Motorsport went somewhere I never expected a racing sim to go. Its Blind Driving Assists are supplemental audio cues that tell low- and no-vision players where they sit on the track and how they're getting through each turn, and Turn 10 built them with direct feedback from blind accessibility consultant Brandon Cole. Hogwarts Legacy, for its part, shipped a high-contrast gameplay mode that paints important characters and objects in vivid colour. Pattern by pattern, the AAA market has built up a real practice.

Industry awareness has shifted too. Accessibility conferences are fixtures on the calendar now, and major publishers pay outside consultants to review their games. The UK charity SpecialEffect, which has spent years helping physically disabled people play, also advises studios and even put together a DevKit that teaches developers about motor accessibility. There's a shared vocabulary as well. Words like "co-design" and "lived experience leads" barely existed in studio meetings a decade ago.

Where Significant Gaps Remain

Blind and low-vision players are still badly underserved. Visual UI and map navigation lock them out, and so do inventory screens and most combat systems. Screen reader support is rare, and when it exists it's often broken, with buttons that do nothing and menus that read in a scrambled order. Worse, status changes often happen without a word. The share of mainstream games a totally blind player can finish from start to end, unaided, is tiny. And that isn't because the design is impossible. It's because audio-first design has never been treated as a commercial priority.

The exceptions prove the rule. A Hero's Call and Frequency Missing, along with a handful of others, show that fully audio gameplay works and can hit hard emotionally. My favourite example is The Vale: Shadow of the Crown from Falling Squirrel, released in 2021. You play Alexandra, a blind princess stuck at a remote keep just as war breaks out, and the game is built almost entirely from sound. None of these titles had a AAA budget behind them.

Audio description, meaning spoken descriptions of cutscenes and visual story moments, is almost absent from games. Film and TV built it into their workflows decades ago, and regulators keep pushing it further. In the US, the FCC's 2023 order phases audio description rules into ten more TV markets every year until all 210 are covered in 2035. Games, meanwhile, still treat it as an afterthought. So a blind player who reaches the cinematic ending of a forty-hour story often gets the dialogue and nothing else, with no clue what's happening on screen. How is that still acceptable in 2026?

Accessible documentation is scarce. Tutorials and strategy guides seldom arrive in formats a screen reader can handle, and fan wikis are worse, with dense visual layouts that screen readers trip over. YouTube guides assume you can see. Even official documentation leans on annotated screenshots. Here's the odd part: a blind player trying to look up how to beat a boss often has fewer resources today than in 1995, when plain-text GameFAQs walkthroughs were the norm.

Small and indie studios don't have the budgets the giants poured into accessibility tooling and testing, and the gap between AAA and indie is enormous and still growing. An accessibility lead and outside consultants cost real money, and so does a dedicated QA pass. Most indie teams know this matters and feel terrible that they can't afford to do it well. I understand that feeling. The missing piece is free accessibility tooling that drops easily into common engines, and that's a structural hole the industry still hasn't filled.

Multiplayer accessibility trails single-player by years. Voice chat without transcription keeps disabled players out of competitive scenes, and so do twitch reaction windows with no configurable assists. Visual-only callouts make it worse. Some games have improved here (Microsoft's automatic chat transcription is a genuine step), but the picture is patchy.

Why EchoQuest Takes a Different Approach

Instead of retrofitting accessibility onto a visual system, EchoQuest starts from the other end. Everything is audio and text first. Images and interface design sit on top of a game that already works without them. I don't have a "blind mode." I have one mode, designed from the ground up to work for sighted and blind players alike.

And that decision reaches right down into the architecture. A screen reader going through EchoQuest's HTML gets clean, meaningful labels, because I wrote them with screen readers in mind from day one. Keyboard users get a logical tab order, since the layout was planned for keyboard traversal first and arranged visually second. Every action has a key, too: Space or P pauses the narration, R replays it, the number keys pick a choice and L tells you where you are. Voice players get commands that map to real game actions, because I picked verbs that are easy to say out loud. The audio description "problem" never comes up at all, because the narration describes every scene by default. The visual layer never displaced audio as the source of truth.

Am I done? Not even close, and I'd rather talk about the bugs I ship by accident, because hiding them helps nobody. Early on I found that choices were being announced and focused while the narrator was still talking, so screen reader users heard two voices at once. Now the choices wait until the narration ends. That same month I added screen reader announcements for HP and inventory changes, which honestly should have been there from the start. Later I discovered the microphone was blocked on EchoQuest's own pages, so voice input quietly didn't work until I fixed it.

I think the best thing I can do for accessible gaming at large is prove that audio-first design can pay its own way and still be creatively rich. Then the industry might see it as an investment instead of charity. Audio-first isn't a downgrade. It's a different way to experience a story, and in many ways a more immersive one. I want to make that case loudly enough to shift the conversation.

What You Can Do

If you're a player who cares about accessibility, the most useful move is to spend your money with studios that take it seriously. Buy from publishers who put out accessibility trailers. Write reviews that name the specific features that worked or failed you. And tell developers when something locks you out, because many of them genuinely don't know.

If you're a developer, the cheapest first step is to play your own game with a screen reader for an hour. Just one hour. It'll hand you enough findings to keep you busy for a month. After that, talk to disabled players directly. The disability advocacy community in games is generous and well organised, and its feedback transforms products. So what would you find if you tried it tonight?

Try EchoQuest free: no account needed for your first session →

Related reading: Browse all EchoQuest blog posts.