1,243 karma · joined May 27, 2022
Email: r.d.t.prater@gmail.com
Maybe they can push it to make the Android accessibility framework more responsive, especially when scrolling the screen with TalkBack, and catch TalkBack up with VoiceOver. Oh and add Accessibility Actions to apps like YouTube so I don't have to swipe through "video name", "video name button", "go to channel button", "more actions button", every, single, video.
But they won't because accessibility is something you have to actually prompt the model to do and who cares about a11y.
If you're reading this, I'd like a favor. I'd like you to read the WCAG, then force all software, including that from OpenAI, Anthropic, Google, Apple, Microsoft, all Linux desktops and packages, especially mobile Linux stuff, oh and did I mention Google, to be accessible, compliant to the highest possible level of the WCAG. Thank you.
For non-FOSS products, it's even worse. There is no way to tell Amazon that, for the past several months, their library view for Kindle on iOS was inaccessible to VoiceOver, with the books having no accessibility label, and the only way one can tell what book they're about to open is through VoiceOver's tiny on-device image describer model. Of course, in iOS 27 (beta currently) this is improved, but it shouldn't have to be. The last few versions of Kindle has begun fixing this, but last time I tried, about a week ago, it could easily break even just by my scrolling the view a few times.
So I don't even bother anymore. If Google can stand having poor Braille support on Android, fine, I'll use an iPhone. If Apple can stand having awful Google Docs support, which I use at work, on MacOS, I'll use Windows or even Linux where it works fine. If an image isn't described, I will put it through AI. If a page doesn't work well with a screen reader, I'll send it through AI too. If I want to play a video game where 99% of them do not have spoken menus, but I can enjoy the actual gameplay, I'll ask AI which menu option I'm on.
I've come to feel that life is so miserable when I and only a few others fight and fight for accessibility. If it works, it only works for a moment. So I just lean on AI because it can "see" a lot better than I can. Besides, people have used AI to make accessibility mods for Final Fantasy 1 through 6, the pixel-remaster versions. So when terminally angry people come at me for my use of AI, I just don't care anymore. Let them go blind and see how it feels.
Well, I have barely anything to show for months of this. I made Termux more accessible on Android, made an MUD client for Emacs, fixed up some Emacspeak stuff because it's been abandonned going on 3 years now, and Emacs packages wait for no one, and tried added Grade 2 Braille entry support to BRLTTY. That failed because depression sucks and who would even use this vibe coded junk anyway.
The more open nature of Android made it rather easier. How far behind in features TalkBack is compared to VoiceOver, besides AI image description, made it feel like trying to heal a broken arm with pain pills. So I'm trying to tell myself that I can't fix everything, and that it's not my fault if other people, and companies, choose to not consider accessibility. I mean I can't help Google if they choose to not be helped.
Ah well, Global Accessibility Awareness Day is this Thursday. Maybe Apple will finally announce LLM image descriptions, and hopefully my iPhone 16 will be good enough for them because I can't afford to upgrade in this economy.
Spoken like a true AI.
And because it's all controlled by me, I can tell it how to have the package speak, what it should ignore, and I'm not stuck with whatever some sighted person at some big company thinks a blind person wants. Everything should at most be open source, and at least be hackable.
All that to say, AI has helped me out a ton. Now I can be as productive as Emacs, and a Linux terminal, and maybe one day a Linux GUI with real Firefox and such, allows. And it would have *never* happened without AI.
So let's please do continue bringing on the AI. Make it smart and local, so I can have continuous AI descriptions right on my phone, with the ability to screen share or even agent-control my phone to get around inaccessible apps. Oh and fix AI app accessibility so the app sends output to screen readers when I type to it cause I hate talking to my phone and not every blind person wants to speak all the time. Ugh I hate that stereotype.
* Made Termux accessible enough for me to use.
* Made an MUD client for Emacs.
Gotten Emacs and Emacspeak working on Termux.
Gotten XFCE to run with Orca and AT-SPI communicating to make the desktop environment accessible.
None of this would have happened without AI. Of course, it's only useful for a few people that are blind, use Android, and love Linux and Emacs and such. But it's improved my life a ton. I can do actual work on my phone. I've got Org-mode, calendar, Org-journal, desktop chromium, ETC. all on my phone. And if AI dies tomorrow, I'll still have it. The code is all there for me to learn from, tweak, and update.
I just use one agent, Codex. I don't do the agent swarms yet.
Now it reads (usually) only newly incoming text, I can feel around the screen to read a line at a time, and cursor tracking works well enough. Then I got Emacs and Emacspeak working, having Gemini build DecTalk (TTS engine) for Termux and get the Emacspeak DecTalk speech server working with that. I'm still amazed that, with a Bluetooth keyboard, I have Linux, and Emacs, in my pocket. I can write Org and Markdown, read EPUB books in Emacs with Nov.el, look at an actual calendar not just a list of events, and even use Gemini CLI and Claude Code, all on my phone! This is proof that phones, with enough freedom, can be workstations. If I can get Orca working on a desktop environment in Termux-GUI. But even with just Emacs and the shell, I can do quite a bit.
Then I decided to go wild and make an MUD client for Emacs/Emacspeak, since accessible ones for Android are limited, and I didn't trust my hacks to Termux to handle Tintin++ very well. So, Emacs with Emacspeak it was, and Elmud [2] was born.
Elmud has a few cool features. First of all, since Emacspeak has voice-lock, like font-lock but for TTS, Ansi colors can be "heard", like red being a deeper voice. Also a few MUD clients have sound packs on Windows, which make them sound more like a modern video game, while still being text-based. I got a few of those working with Elmud. You just load one of the supported MUD's, and the sound pack is downloaded and installed for you. It's easy and simple. And honestly, that's what I want my tools to provide, something I, or anyone else who chooses to use them, that is easy to get the most out of.
None of this would have been possible without AI. None of it would have been done. It would have remained a dream. And yes, it was all vibe-coded, mostly with Codex 5.2 on high thinking. And yes, the code may look awful. But honestly, how many closed-source programs look just as bad or even worse under the covers of compilation?