nvaccess
Do not emit spelling error reporting when speech is on-demand or off
Context: I am using on-demand speech mode when in visio-conference to be able to listen without being disturbed by automatic NVDA audio feedback.
Steps to reproduce
- Check that "Play sound for spelling errors while typing" is enabled in keyboard settings
- Enable on-demand speech mode
- Open Word and type misspelled text.
Actual behavior
The spelling error buzzer is heard.
Expected behavior
No feedback sound should be reported.
NVDA logs, crash dumps and other attachments
N/A
Additional considerations
Other reporting sounds should also be considered when designing a solution. Maybe some of them should not be reported either in on-demand or off speech mode? Discussion is open
Considering the on-demand speech mode during conference use case, I'd say that the following should not be reported either:
- Progress bars ("Progress bar output")
- Auto-suggestions ("Play a sound when auto-suggestions appear")
Maybe there are other use cases that would require them to be reported in off or on-demand mode though.
For progress bars, you can test with:
But the following should remain reported IMO, even in conference using on-demand mode:
- Beep if typing lowercase letters when caps lock is on
Indeed, it reports an error, but that should never happen in the first place.
At last, the type of sound being reported should also be considered: beeps or spelling error buzzer are quite disturbing during a conference, while auto-suggestion open/close sounds are much less invasive.
System configuration
NVDA installed/portable/running from source
installed
NVDA version
2025.3.2rc1
Windows version
Windows 11 23H2 (AMD64) build 22631.6199
Name and version of other software in use when reproducing the issue
N/A
Other information about your system
Other questions
Does the issue still occur after restarting your computer?
Yes
Have you tried any other versions of NVDA? If so, please report their behaviors
No
If NVDA add-ons are disabled, is your problem still occurring?
Yes
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?
Not tested, unrelated
