Re: NVDA pronouncing "no" as "number" with some widgets but only with Microsoft synthesizers
toggle quoted messageShow quoted text
It's the Microsoft Synthesizer trying to be helpful and assume that "no" = "number". The two actions I can suggest are:
1) Report it to Microsoft's Disability Answer Desk, and request their synths not make those assumptions.
2) You can use NVDA's speech dictionary to add an entry for "no" to try to prevent it. It would be worth testing whether it is case sensitive (eg is "No" treated the same as "no", or "NO"), in which case you could make a entry to change "No" (whole words only) to "no". Just remember if you are proof reading something and looking for missed capitals :)
On Thu, Sep 12, 2019 at 5:13 AM slugolicious via Groups.Io <email@example.com> wrote:
If a <select> element has "yes" and "no" options, "no" is pronounced as "number" when using any of the Microsoft synthesizers (Microsoft Speech API version 5, Microsoft Speech Platform, Windows OneCore voices). It works ok with eSpeak.