@28
If you understand how trivial all of this is for the sighted and you understand how bad it is for us by comparison, you'd be as mad as I am, especially since we can trivially do better with the amount of money the blindness orgs are sitting on and spending on stupid things. Look at the Holman prize winners sometime (I'm not sure that's still running). Light House for the blind handed out a huge amount of money to one-off things that help only one or two people instead of important things that could benefit us all. We do that all the time. It's a terrible waste.
I'm perfectly willing to admit VSCode changed my life and made Synthizer happen twice as fast. Like, that's seriously how much good tooling matters. Start stacking yourself up to sighted coworkers and stuff and you work harder for the same level by a lot. We've had other IDEs before VSCode but they all had problems of one sort or another. VSCode also has problems but it's the first one that doesn't just fall down. But the thing is that sighted coders barely type their code. It's all "I typed two letters and said yes this is what I want, then clicked build, then all the problems were in red with hints how to fix them" except that in modern IDEs you don't even hit build to find out what your errors are. The Quorum people could have been working on giving this to us 5-10 years ahead of when we got it, and then kept going and done better, all before VSCode was even on the radar. But their terminal value isn't actually helping blind people code, they've just ended up in a place where they're pulling that sort of energy and perception to themselves. But again: it's not nearly so bad as things like Mathplayer, because no matter how far they pull the worst they can do to those of us who code professionally is nothing.
The problem is that unless you're experienced enough you don't see the problems. But because of the problems it's really hard to get experienced enough. Then everyone develops off the vast majority who need to learn. Then we all go "huh, I wonder why blind people don't have jobs" and it's just like, you realize that you could fix this by just going to orgs that make job-oriented software and giving them a million dollars? I bet Jetbrains would totally have made their IDE accessible for a million dollars, for one thing. Quorum has probably easily spent well into the 6 figure range, but a million certainly isn't out of the question if not more, and the blindness orgs definitely have that kind of money. The path out of Quorum for the sighted is grab any IDE, install it, and just go. The path out of Quorum for the blind is learn to configure your screen reader, discover that IDEs suck and you'd better learn the command line, figure out how to efficiently navigate the inaccessible CI pipeline site, and so on, just tons and tons of edges. The path out of mathplayer is even worse because learning LaTeX is not a trivial exercise.
you don't solve the problem for experienced people who need to use these tools in anger by solving them for students and other people getting started. You have to work from the perspective of making it useful and scalable, then figure out how to teach it. Writing this stuff in a format that's teachable means that as soon as it leaves the classroom it just breaks. But writing this stuff for the classroom means that there's very little reason to fund it again because the work is perceived as having been finished and it's very hard to convince people that that's not the case if they can point to a bunch of students getting good grades because students getting good grades is a measure we have tied to success even though it actually really doesn't matter at all. In the case of Quorum, whether they want to be perceived this way or not, they've done a good job of becoming that language for blind people, and the only saving grace is that they're still small enough to not have sucked everyone blind who might take a programming class in. To be honest it's hard for me not to see it as them failing to get traction in sighted land, and then pivoting to use us as a sort of captive audience, but admittedly that's probably not how it happened. Even so, as far as I can tell that's nonetheless where it is.
@ethin
I agree that that's noisy, but when you put Mathjax in plain source mode or Wikipedia in LaTeX rendering mode you can often get just the math parts of the document in LaTeX, with the rest formatted via normal HTML. That particular path is much better, when you can get away with it (which, among other places, is all of Stack Overflow).
But again I'm not saying LaTeX is great. They both suck. It's not that LaTeX is amazing, it's that LaTeX is scalable in the sense that LaTeX doesn't fail as you continue to push the envelope and that you can get it as the output of a lot of things. Admittedly I should try MathML with my braille display sometime, but braille is just so terribly slow and these days I'm too busy coding, Wikipedia and SO give me LaTeX, and there's just no need. But MathML is actually almost one-for-one Nemeth, so that probably at least works out (or could, maybe it's buggy). Except that braille doesn't top 100 words a minute which is in itself a problem.
My BlogTwitter: @ajhicks1992