@marco hi, Marco.
I’m not blind. But I have been designing and writing code for over 25 years. And accessibility has been a priority for me since day one. I even write articles about accessibility in design/tech.
I’m curious about this poll. Are some editors more functional with VoiceOver? Or are you just curious with respect to community?
I’m on a Mac (always have) and I’ve used many editors. Currently I use Nova.
@marco thanks for sharing that. I’m gonna follow your poll because I’m curious about the results.
For many years I used Text Mate, then for many more I used Sublime Text. I really loved Atom before Microsoft destroyed it. After that I wasn’t sure what I wanted to use.
I’ve been using Panic software for as long as I can remember. It began with Transmit. Nova is great. But I’m sight-abled, so for me it may be a privilege to use it.
@miki @marco Ah, so it’s because the controls are being rendered inside the “sandbox” of a graphical output instead of native system controls being used? (Sorry for the layperson speak)
That’s disappointing, and seems like a big software design hurdle to shift from now, if they decide to do the right thing and support accessibility.
@bntn @marco Yeah, Zed is basically telling the system something like "render these pixels, of this color, at these coordinates", not "here's a button, put it inside this window."
This is a massive oversimplification, it uses GPU acceleration a lot, which means a lot of that info isn't even calculated by the ap, but directly by the GPU.
Screen readers are a bit of a misnomer, they don't actually read the screen, they need the to get the semantic info about what controls are present from the system. If all the system knows about is pixels, then all the blind person sees is a blank window.
@bntn Yes exactly.
Putting your UI in a canvas would produce the exact same result, total and utter inaccessibility on your page.
There's a way around it, you can create a fake accessibility tree that reflects your app's understanding of what controls actually are on the screen. This is what web browsers do, for example, along with third-party GUI toolkits like QT or Java.
The web dev equivalent of that would be a completely unstyled, visually hidden model of the UI in the DOM, created only if there is a screen reader running, that reflects what's displayed on the canvas. Google DOCs's Braille Mode uses this trick to make Docs accessible.
@mitchellh Glad to hear it is being addressed on macOS, and sad to hear the situation on Linux. I think I’ve seen @aral raising a stink over accessibility limitations over there.
Please prioritize shipping these 🙏🏻
@bntn @mitchellh Yeah, I’m back to using a Mac as my daily driver after six years on Linux because of this.
This was the last straw: https://ar.al/2024/06/23/fedora-has-been-shipping-with-a-broken-screen-reader-for-nine-years-but-the-real-problem-is-me/
@marco What on earth is the point of a text editor which only runs on one platform? It means you have to learn a different editor for each platform you use, and no-one has that much learning time to waste.
I do use Visual Studio Code, not because Iike it, but because it works the same everywhere and supports all the languages I need to use well.