I am very curious and want to help to make Linux more accessible.

I wrote with some people and got some insights:

  • everything text, like a read-mode-only browser or a plain Terminal is best for TTS engines.
  • TTS engines are difficult, some are really good but need many resources, some are worse but save resources
  • TTS needs to be optimized to be really fast in some cases, to keep up with the speed
  • some apps are better, some are worse, but probably most apps dont really suit blind people, as the whole GUI concept makes no sense

I am really curious. How would it be best for you, braille vs. voice, voice input vs braille vs. gestures?

What apps do you find best, how do you browse the web, find media to listen, how do you use Document editors and what purpose do they have for you?

Thanks a lot!

  • Samuel Proulx@rblind.comMEnglish
    1·
    1 year ago

    But it does make assumptions. It assumes I can see the monitor and read printed text. I’d have no problem with it failing on error, if that failure always made sound. There are BIOS firmwares that can play mp3 files, and DOS could make noise via the PC speaker, for God’s sake. There’s no excuse for Linux’s ableist assumptions.

    • Illecors@lemmy.cafeEnglish
      11·
      1 year ago

      I’ll stick to what I said before - it doesn’t. You can command it to make noise, but it has to be an active decision.

      • Samuel Proulx@rblind.comMEnglish
        11·
        1 year ago

        But you don’t have to command it to print text on the screen. That doesn’t need to be an active decision. Your assumptions are still showing.