Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NVDA does not play the buzzer sound in word when a speeling error is made #12161

Closed
fatihyuksek1 opened this issue Mar 13, 2021 · 4 comments · Fixed by #12925
Closed

NVDA does not play the buzzer sound in word when a speeling error is made #12161

fatihyuksek1 opened this issue Mar 13, 2021 · 4 comments · Fixed by #12925
Milestone

Comments

@fatihyuksek1
Copy link

Steps to reproduce:

  1. Open word
  2. Enable "use UIA automation when accessing word documents" under NVDA settings/advanced
  3. misspell a word and press space
  4. NVDAS doesn't play the buzzer sound to indicate that you've made a mistake

Actual behavior:

NVDA doesn't play the buzzer sound to indicate a spelling error

Expected behavior:

NVDA will play the buzzer sound when a spelling error is made when it is enabled under document formatting settings

System configuration

NVDA installed/portable/running from source:

Installed

NVDA version:

2020.4

Windows version:

windows 10 2004

Name and version of other software in use when reproducing the issue:

Words 365 latest version

Other information about your system:

I have the report spelling errors setting checked under the document settings diolog. Previously NVDA would play the sound but now it doesn't. I have the uia automation turned on under the advanced settings category as well

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 add-ons are disabled, is your problem still occurring?

Did you try to run the COM registry fixing tool in NVDA menu / tools?

no

@burakyuksek
Copy link
Contributor

Turning off UIA fixes the issue but then we lose the performance improvements it causes.

@lukaszgo1
Copy link
Contributor

@michaelDCurran According to the reporter of #12915 this issue still persists. It would be good to fix this if possible for 2021.3 since having indication of spelling errors as you type is a pretty useful feature and it no longer works for build of Office where UIA has been enabled by default.

@CyrilleB79
Copy link
Collaborator

I hope it can bee fixed in NVDA 2021.3.

If not, (or if there is another regression using UIA), there are two path:

  • Revert the commit forcing UIA use for recent versions of Word
  • Modify the option "Always use UI Automation to access Microsoft &Word document controls when available" to "use UI Automation to access Microsoft Word document controls" and a combobox with the following choices (as per Edge/Chromium):
    • Yes
    • No
    • Only if necessary
    • Default (only if necessary)

@andrew-l-d
Copy link

I have closed #12915, as it duplicates this report. Re Check Spelling as you Write, with UI Automation not enabled in 2021.2 and previous, the buzz is still activated when an unrecognised word is written. My preference is not to check spelling as I write due to Word sometimes stealthily changing a word I intended to use when Check Spelling is enabled.
Andrew

michaelDCurran added a commit that referenced this issue Oct 13, 2021
…12925)

Fixes #12161

Summary of the issue:
When in any editable text control (E.g. a Word document), each time the user completes a word by typing space or another punctuation character, NVDA checks the formatting of the completed word to see if it is marked as a spelling error, and if so plays a special text error buzz sound.
However, in at least MS Word with UIA, this check for spelling errors never really finds an error as MS Word has not yet actually detected the error itself.
We need to slow down NVDA's detection to give the app more time.

Description of how this pull request fixes the issue:
Delay the fetch and check of the completed word's formatting into a future core cycle (specifically a 50 ms delay) to give the app more time to detect the error itself.
@nvaccessAuto nvaccessAuto modified the milestone: 2021.3 Oct 13, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants