@FreakyFwoof @ToniBarth @TheQuinbox Good point about the advantages of externalizing the screen reader output, despite the obvious drawback for self-contained portability.
-
@FreakyFwoof @ToniBarth @TheQuinbox Good point about the advantages of externalizing the screen reader output, despite the obvious drawback for self-contained portability. It would have been beyond Ableton to reproduce the breadth of TTS and Braille options on Windows, iOS, or Android, let alone the choice of all three. They presumably realized that and decided to punt on that. Competing priorities, limited resources, tradeoffs everywhere.
-
@FreakyFwoof @ToniBarth @TheQuinbox Good point about the advantages of externalizing the screen reader output, despite the obvious drawback for self-contained portability. It would have been beyond Ableton to reproduce the breadth of TTS and Braille options on Windows, iOS, or Android, let alone the choice of all three. They presumably realized that and decided to punt on that. Competing priorities, limited resources, tradeoffs everywhere.
@FreakyFwoof @ToniBarth @TheQuinbox Now, maybe that points to the need for a better shared platform for devices like the Move, a platform that has the accessibility ecosystem already built in. Some of us wanted Android to become that. But that didn't really happen; Google only really cares about their own devices plus the emulator, so you end up with Android forks for other devices, and no official maintained port for the Pi as far as I know.
-
P pixelate@tweesecake.social shared this topic
