Word 2010: While performing a spell check,  initiated with F7, there are times, where NVDA will not read context and speak/read spelling mistake #1938

Closed
nvaccessAuto opened this Issue Nov 20, 2011 · 7 comments

2 participants

@nvaccessAuto

Reported by kevinchao89 on 2011-11-20 07:17
Word 2010
winwordTextInproc-4800

Within Docs;
have a lengthy document with a variety of spelling mistakes, some with or without suggestions;
F7 for spell check;
Ignore or accept correction.

Expected: NVDA to always read context, spell mistake, and read suggestion/spell
Actual: Sometimes NVDA will be absolutely silent.

Regression: No

@nvaccessAuto

Comment 1 by manish on 2013-08-29 03:26
The spell checker (_WwN) window raises an IAccessible object_focus event (as seen in AccEvent.exe) every time the context changes (e.g. when the user presses alt+i or alt+c and the next spelling error is displayed).
However, NVDA seems to ignore this IAccessible event -- I guess because the same window was in focus before this IAccessible object_focus event was raised.
Is there some way I can have NVDA not ignore the focus events even if those are for the currently focussed window?

@nvaccessAuto

Comment 2 by jteh on 2013-08-29 03:34
Ug. That's an ugly implementation. You can try overriding isDuplicateIAccessibleEvent.

@nvaccessAuto

Comment 3 by manish on 2013-08-30 07:12
Overriding the IsDuplicateIAccessibleEvent and returning false fixed the problem. I tested this with office 2010 and 2007 and it works in both.
The fix is available at:
https://manish_agrawal@bitbucket.org/manish_agrawal/nvda.git
branch: t1938

The results in a document with lots of bolded text are much better with the fix for #3431 also included.

Regards,
Manish

@nvaccessAuto

Comment 4 by manish (in reply to comment 3) on 2013-10-18 13:44
Replying to manish:
Have created a new branch that is created from master instead of next as was the case for the branch I submitted earlier.
The new branch is in_t1938
available at:
https://manish_agrawal@bitbucket.org/manish_agrawal/nvda.git

Overriding the IsDuplicateIAccessibleEvent and returning false fixed the problem. I tested this with office 2010 and 2007 and it works in both.

The fix is available at:

https://manish_agrawal@bitbucket.org/manish_agrawal/nvda.git

branch: t1938

The results in a document with lots of bolded text are much better with the fix for #3431 also included.

Regards,

Manish

@nvaccessAuto

Comment 7 by Michael Curran <mick@... on 2014-12-03 08:11
In [a3808fd]:
```CommitTicketReference repository="" revision="a3808fd2dd575d2ed84a56aded3ca59812ac8890"
Merge branch 't1938' into next. Incubates #1938

Changes:
Added labels: incubating
@nvaccessAuto

Comment 9 by Michael Curran <mick@... on 2014-12-18 03:35
In [9e203d0]:
```CommitTicketReference repository="" revision="9e203d0f7565f633ed85032030cdbf00761b8869"
Merge branch 't1938'. Fixes #1938

Changes:
Removed labels: incubating
State: closed
@nvaccessAuto

Comment 10 by mdcurran on 2014-12-18 03:36
Changes:
Milestone changed from None to 2015.1

@nvaccessAuto nvaccessAuto added this to the 2015.1 milestone Nov 10, 2015
@michaelDCurran michaelDCurran added a commit that referenced this issue Nov 23, 2015
@manish10 manish10 fix for #1938 - misspelled word is automatically spoken in the spell …
…check dialog in word.
824fb70
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment