The Ghost D-Pad and Why “Good Enough” is Failing Android Braille Users

For most people, a software update is a minor curiosity—a new icon here, a slightly faster app there. But for those of us who navigate the digital world through Braille Displays (hardware devices that use rounded pins to physically represent Braille characters), an update can be the difference between a tool that empowers us and one that locks us out.
Recently, the rollout of TalkBack 16.2 (Android’s screen reader) and the broader Android 16 system update have highlighted a growing, frustrating reality: On Android, accessibility is often treated as a checklist of “good enough,” while Apple treats it as a standard of excellence.

The Ghost D-Pad: A TalkBack 16.2 Failure

Imagine you are driving a car, and suddenly, your steering wheel stops turning the tires. Instead, it tries to operate a joystick that isn’t even installed in your dashboard. You are stuck.

That is exactly what happened with the Humanware NLS EReader. This is a specialized Braille display provided to blind people across the U.S. through the National Library Service (NLS). In the TalkBack 16.2 update, the software replaced the “Line Up” and “Line Down” commands with “D-pad” (Directional Pad) commands.
The problem? The NLS EReader doesn’t have a D-pad.

Google remapped the input to a physical button that doesn’t exist on the hardware. Because there is currently no way to remap these Braille commands, users are effectively trapped. If I’m in the Audible app and want to skip past ten different filter buttons to get to my first book, I can no longer move “down” by lines. I have to press Enter with dot 4 through every single individual element just to find my content, instead of pressing space with dot 4 to move down vertically to find the first book.

The Illusion of Customization

Android’s selling point has always been customization. But for Braille users, that’s a myth.

Contrast this with iOS. Apple is often criticized for its “walled garden,” yet their Braille access works seamlessly about 80% of the time. On an iPhone, I have full system-level control:

• Enter my PIN to unlock my phone directly from the display. No need to pull out my phone or move number by number to find the ones for my PIN, and press Enter on each one, like entering a character name with a game controller, or typing your name using nothing but tab and enter instead of the letter typing keys.
• Complex Keyboard Commands: Using specialized Braille chord commands (specific combinations of dots), I can emulate a physical keyboard’s Modifier Keys—like Command, Control, Option, and Shift.
• Seamless Shortcuts: This means I can use Command + N to start a new email in the Mail app or use system shortcuts to switch apps without ever touching the phone screen.

On Android, I am left “floundering” until I find a workaround or install a custom launcher that might—just might—work.

Android 16: Clutter and Information Loss

Beyond the screen reader, the Android 16 system update has introduced “clutter” and removed vital context that makes the phone harder to use:

• Notification Blindness: In a collapsed stack of notifications, the system no longer tells me which app the notifications belong to. Previously, I might hear “collapsed, Messages, 5.” Now, I just hear “5.” I am left guessing which app those five notifications are from.
• Redundant Labels: When I do check notifications, I now have to listen to the screen reader say “fully expanded”—extra verbal clutter I have to read or hear before I get to the actual message.
• Threaded Emails: Navigating a conversation in Gmail is still a labyrinth, making it nearly impossible to skip from one message to the next in a thread.

The OnePlus 13: Hardware Apathy

It isn’t just Google; it’s the manufacturers. I am currently using the OnePlus 13, and the lack of care is staggering. When I first got the device in February 2025, the fingerprint guidance was broken—it would tell me to “move up” even if my finger was already way above, to the left, or to the right of the sensor.

I emailed OnePlus. I posted on their forums. I received nothing but canned responses. Now, after the latest updates, the guidance is simply gone. Instead of fixing the guidance for blind users, they just removed the feature entirely. While I am seeing these specific hardware failures on my OnePlus, this apathy is felt across the Android ecosystem.

Good Enough is No Longer Enough

Google’s image descriptions (using AI to tell a blind user what is in a photo) are great. But image descriptions are “flashy” accessibility. Braille support is “infrastructure” accessibility—and the bridge is collapsing.

When I’m on Android, I find myself hating the experience of using Braille. That is heartbreaking because Braille is literacy; it is independence. Google seems to strive for a product that “meets basic needs.” But as Apple continues to advance, “good enough” is no longer usable. We don’t want to have to pull out our phones and tap a glass screen to fix a software error. We want our tools to work. We want these companies to listen to us.

I don’t know how the VoiceOver team makes Apple’s apps work so well with VoiceOver. If they script the Mail app to allow us to move from one message in an open conversation to another with a single swipe, that’s great. If they script the Books app to go to the next page when VoiceOver reaches the end of the current one? That’s wonderful. I’m to the point where I don’t care if valiantly sticking to “the screen reader should just read whatever Android can scrape out of the creations of apathetic app developers” isn’t a priority to me anymore because it doesn’t work. Clean screen reading has shown, by the number of people still using JAWS and NVDA over narrator, that you can’t get as much done with it than you can when you script apps to be easy to use and not just technically accessible. If scripting works, they should do it.

I want to use my phone, not be an accessibility tester every minute of every day. Being a blind person with a job and low energy in the first place, I need a time when I can almost, almost forget I’m blind and enjoy a book or play some Dragon Ball Z or Dissidia Final Fantasy. Luckily Apple allows emulators on the App Store, and Retroarch and VoiceOver recognition work well enough to allow me to play some games. Retroarch on android doesn’t have an accessibility element which TalkBack can grab onto. Luckily I’ve found an app, ClassicBoy, which is an all-in-one emulator that *does* have this accessibility element, so I can use that. But this just highlights that we have to look high and low for accessibility on Android, whereas on iOS it’s just there.

Another experience that highlights this is IRC clients. IRC is an older, yet still alive, chat system. On iOS, there is an app called Igloo which mentions VoiceOver accessibility, and even has settings in the app that control what is announced in channels. I couldn’t find a single Android app for that which offers such a level of accessibility and yes, customizability. Developers know about VoiceOver on iOS, but do not know about TalkBack on Android. And with how Google treats TalkBack and accessibility, can we blame third-party developers?

Of course, sometimes it goes the other way. Browsing through Reddit, or getting pictures in messages, on iPhone, I miss TalkBack’s instant, pretty good AI image descriptions. But at this moment in my life, it’s not worth the grinding frustration of every time I pull down the notification shade, remembering just how little Google and OnePlus care about accessibility, and reminding me that yes, I’m blind, and that yes, we blind people are an afterthought at best, and completely invisible to these large companies at worst, and nothing we can say or do will change a thing because we’re like ants trying to get the attention of an avalanche. We will be crushed, no matter what. change my mind. I dare you.

A Brief Glossary for Sighted Readers

• Braille Display: A tactile device that connects to a phone via Bluetooth. It has pins that move up and down to create Braille characters in real-time.
• TalkBack: The Google-developed screen reader for Android.
• Modifier Keys: Keys like Command or Control that change the function of other keys.
• D-Pad (Directional Pad): A physical four-way directional control, which many Braille displays (including the NLS EReader) lack.