I hate that so much. When blind people are trying to start JAWS (the screen reader) by typing "jaws" into the start menu and pressing Enter, it will sometimes pull up a Bing page on Jaws the movie instead. And the blind person is just sitting there waiting for the screen reader to start. I tell people to use the run dialog for that reason. Sucks but that's what you have to do in the age of inshittisoft.
Linux is even getting more accessible. I'm thinking of Elementary OS which not only posted about their accessibility work, but linked to the articles which really fired things up. I'm a Fedora guy, mainly because I want the latest Orca, AT-SPI2 and such, so I don't feel like an Ubuntu dirivitive would work as well.
So I installed Fedora on my work machine and find that I can still get all of my work done. Well except the parts that require testing accessibility on Windows screen readers or helping with Windows-related issues.
The only thing I miss now are the many addons made for NVDA, especially the ones for image descriptions. But if I can get something to work with Wayland, I could probably vibe code some of them. Thank goodness for Claude Code.
This. Why do features like this always get swept under the rug? Accessibility could be a major feature Firefox gains revenue on. Make it paid, if absolutely necessary. Instead of hopping on the latest hype train.
Wow, I never heard of that before today. Sega Genesis was my first console. I still remember the six button controller. It worked well for Mortal Kombat 3.
Emacs and Emacspeak make me feel something. A lot of something. This kind of "playground" feeling where I can dive into a manual that's just sitting right there. The the entire Emacs is a manual. C-h m and boom, all keyboard commands for that mode are right, feaking, there. No hidden bullcrap, no patchwork HTML tables to drudge through, nothing. And if something doesn't work with Emacspeak, I can Codex it into working. Maybe. Enough to get what I want done, done.
reply