Question for developers of blindness-specific apps who have worked with both the Windows screen reader APIs (e.g. NVDA controller client and the others exposed by Tolk) and speech-dispatcher on Linux, e.g. @draeand and @nolan: When it comes to TTS output that respects a screen reader user's preferences, does speech-dispatcher work as well as the Windows screen reader APIs? If not, what gaps does it have?
Replies:
1
Boosts:
2
@matt @draeand @nolan One problem with Speech Dispatcher versus NVDA Controller or the JAWS COM API is that it won't use Orca's speech rate and it’s less obvious for users how to change the default Speech Dispatcher speech rate, since you have to edit speechd.conf. There have been a few users confused about this for Minecraft Access. But at least it’s better than on MacOS, where there's no way to make AVSpeechSynthesizer use either VoiceOver's speech rate or the speech rate set in speech settings. In Minecraft Access I had to add a speech rate setting to the settings just for MacOS, because that is the only way the user can set it.
