@gnomelibre @objectinspace @techsinger @jorge blindspaining the accessibility of Linux has nothing to do with yourcommand of English.

So, this will be my last contribution to this thread, and, you, in particular. Not for lack of interest or an unwillingness to teach, but, you mentioned that Apple and or Microsoft, and, I'd even extend Google into this pool, that they have money so can dedicate resources to accessibility but there's a key thing they all do that, so far, few or even no distro or otherwise maintainer has done. Listen to the users without pointing the finger back at them. That requires no money. This is key. You say you want feedback and you really want to learn, but you actually dismissed other blind professionals in this thread, people with decades of experiences, and then told them, even, that they were wrong and that it works just fine for you, but then you said it yourself you're not disabled. You didn't listen, you immediately went on the defensive and then made us prove ourselves to you. Apple, and Microsoft, don't behave like this. They also understand that accessibility is as good as the tech infrastructure, and make it usable and accessible from the ground up. My biggest issue with you, and others like you, in the #Linux space, is that refuse to really, and I mean really, listen, to what experts are saying. I've used accessible Cocanut on a VM, and it is a good start. The point is that the ORCA infrastructure needs a lot of work and then some. You all really, and I mean really, need to understand why these bigger tech companies and even other #OpenSource developers actually take the time to get feedback from Disabled users, but not through pull requests or complicated ticket tracking. Come to where the lowest tech people are and get feedback, like these other tech companies do. I use a ton of fantastic #OpenSource tools on Windows because the devellopers actively engage with the community and don't just point and say learn tech! Or it works for me, even though you do not know how to use a screen reader properly. Listen instead of pointing. @gnomelibre @anantagd @objectinspace @techsinger @jorge

@fireborn However, if people just say that things suck, that's completely useless to developers, even for Joanie, as she can't make sense of any priorities from tat blanked statement. So, what would you fix, and in what order? I'd personally start with the keyboard monitoring support under Wayland, but you might have other things in mind?

@modulux @objectinspace @gnomelibre @anantagd @techsinger @jorge
Is it possible/ efficient for some uses (not everything, I know, and not everyone) to simply use CLI display on a braille machine?