So, after JAWS, NVDA is also kissing goodbye to SAPI 4 TTS engines, in 2026.
The support for Microsoft Speech API version 4 synthesizers is planned for removal in NVDA 2026.1. Any remaining users of SAPI4 speech synthesizers are encouraged to choose a more modern speech synthesizer.
https://github.com/nvaccess/nvda/pull/17599
@NVAccess
Fix SAPI 4 driver by SaschaCowley · Pull Request #17599 · nvaccess/nvda

Link to issue number: Fixes #17516 Summary of the issue: After the move to exclusively Windows core audio APIs, the SAPI4 driver stopped working. Description of user facing changes The SAPI4 driver...

GitHub
@amir If anyone is using a SAPI 4 synthesizer and cannot switch (E.G. because it is the only synth they are aware of in their language), please do let us know. We don't want to leave anyone stuck using an older version purely because of this, and if we can help track down a more modern resource which will fit the bill, then we're happy to help.
@amir @NVAccess what about the people with processing difficulties that that’s literally the only thing they can comprehend? I don’t personally know of anyone like that, but I know it’s possible because certain people struggle if they are forced to use any speech synthesizer other than the one they know for 1,000,000% sure they can understand.

@evilcookies98 @amir That's why I asked anyone with a specific example to reach out, so we can look at options with them.

In order to continue using SAPI 4, it would need to be updated to WASAPI. As noted by Matt Campbell elsewhere in this thread, that may be possible, and we could consider a PR for that. Or someone could likely relatively easily create an add-on even with the current implementation. At the end of the day, if someone really needed, they could stay with an older version of NVDA

@NVAccess @amir I myself probably won’t be updating past that point just because that’s yet another choice technology is taking away. Not pointing fingers at you. Not something I use frequently, but I like having the option to use it. Used to be my daily driver back when I started working with windows. If I’m pointing fingers, did anybody with this one? It’s Microsoft for being so darn uncooperative
@evilcookies98 @NVAccess As saddening as it is, this is the nature of technology. And don't forget that JAWS devs ditched SAPI 4 support a long while ago, without even bothering to ask people about the consequences of the decision.
@NVAccess @amir I didn’t even think Jaws ever had it. They’ve depended on their own synthesizer for so long, the fact that they even have sapi five blew my mind.
@evilcookies98 @NVAccess They depend on Eloquence just as NVDA depends on ESpeak-NG, Windows OneCore voices, etc.
@NVAccess @amir first time I handle jaws was in 2013 or 2014 and I couldn’t find squat in the way of being able to change it
@evilcookies98 @NVAccess JAWS has always had the ability to alter TTS engines as in the past it had SAPI 4 support as well as RealSpeak/ Solo support, apart from Eloquence.
@amir @NVAccess must’ve been very well hidden 12 years ago. I surely couldn’t find it. I know where it is now but that’s now.
@evilcookies98 @NVAccess LOL - I don't think it has been hidden. It's always been the same like their TTS selection hot keys.