Describe the bug
subsystem screenreader does not seem to honor the selected Android TTS engine in WSA.
I installed Vocalizer and selected it as the default Text-to-speech engine. The setting appears to apply correctly, and live checking showed:
tts_default_synth=es.codefactory.vocalizertts
However, TalkBack still speaks with the Microsoft/Mark voice.
Logs show Vocalizer being selected and bound, but TalkBack then binds back to Microsoft’s WSA speech service:
com.microsoft.windows.userapp
Steps to reproduce the issue
Install a third-party Android TTS engine in WSA, for example Vocalizer TTS.
Open WSA Settings.
Open the Android accessibility or Text-to-speech settings page.
Go to Text-to-speech output.
Open Preferred engine / Default engine.
Select Vocalizer instead of the Microsoft/Mark engine.
Confirm the warning dialog if Android asks whether to allow the selected TTS engine.
Go back to the Text-to-speech output screen and confirm Vocalizer is still selected.
Turn on the WSA screen reader / TalkBack.
Navigate around WSA with the screen reader.
Listen to the speech output.
Notice that TalkBack still speaks using the Microsoft/Mark voice instead of Vocalizer.
Expected behaviour
The WSA screen reader / TalkBack should use the selected Android default TTS engine.
Downloaded Build Of WSA
WSA_2407.40000.4.0_x64_Release-Nightly-with-magisk-30.6.30600.-stable-GApps-13.0.7z
Windows build number
Windows 11 Pro 25H2, build 26200.8875
PC Specification
Manufacturer: LenovoModel: 82LMSystem type: x64-based PCCPU: AMD Ryzen 7 5700U with Radeon Graphics, 8 cores / 16 logical processorsRAM: 16 GBGPU: AMD Radeon GraphicsGPU driver: 31.0.21925.1001
Additional context
No response
Describe the bug
subsystem screenreader does not seem to honor the selected Android TTS engine in WSA.
I installed Vocalizer and selected it as the default Text-to-speech engine. The setting appears to apply correctly, and live checking showed:
tts_default_synth=es.codefactory.vocalizertts
However, TalkBack still speaks with the Microsoft/Mark voice.
Logs show Vocalizer being selected and bound, but TalkBack then binds back to Microsoft’s WSA speech service:
com.microsoft.windows.userapp
Steps to reproduce the issue
Install a third-party Android TTS engine in WSA, for example Vocalizer TTS.
Open WSA Settings.
Open the Android accessibility or Text-to-speech settings page.
Go to Text-to-speech output.
Open Preferred engine / Default engine.
Select Vocalizer instead of the Microsoft/Mark engine.
Confirm the warning dialog if Android asks whether to allow the selected TTS engine.
Go back to the Text-to-speech output screen and confirm Vocalizer is still selected.
Turn on the WSA screen reader / TalkBack.
Navigate around WSA with the screen reader.
Listen to the speech output.
Notice that TalkBack still speaks using the Microsoft/Mark voice instead of Vocalizer.
Expected behaviour
The WSA screen reader / TalkBack should use the selected Android default TTS engine.
Downloaded Build Of WSA
WSA_2407.40000.4.0_x64_Release-Nightly-with-magisk-30.6.30600.-stable-GApps-13.0.7z
Windows build number
Windows 11 Pro 25H2, build 26200.8875
PC Specification
Manufacturer: LenovoModel: 82LMSystem type: x64-based PCCPU: AMD Ryzen 7 5700U with Radeon Graphics, 8 cores / 16 logical processorsRAM: 16 GBGPU: AMD Radeon GraphicsGPU driver: 31.0.21925.1001
Additional context
No response