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

Microsoft Word save confirmation not reported #1538

Closed
nvaccessAuto opened this issue May 31, 2011 · 4 comments
Closed

Microsoft Word save confirmation not reported #1538

nvaccessAuto opened this issue May 31, 2011 · 4 comments
Milestone

Comments

@nvaccessAuto
Copy link

Reported by ink on 2011-05-31 21:16
NVDA does not often read dialog prompts or the highlighted items, e.g., closing MS Word document asking whether file si to be saved... Similarly, in Windows' user account prompt, NVDA fails to read it.

@nvaccessAuto
Copy link
Author

Comment 1 by mdcurran on 2011-05-31 22:46
I am concerned that we're not reading the dialog text for the MS Word confirmation dialog. Could you please state exactly what version of MS Word, and possibly when this boken in NVDA, if ever?

@nvaccessAuto
Copy link
Author

Comment 2 by jteh on 2011-06-01 00:06
Adjusting summary to narrow scope to one single issue. Please file separate tickets for any other issues.
Changes:
Changed title from "Dialog prompts or highlighted items are not often spoken." to "Microsoft Word save confirmation not reported"

@nvaccessAuto
Copy link
Author

Comment 4 by briang1 on 2011-06-01 07:39
Hmm, I've seen this. I don't think its that its not being read, but that its intermittent due to system lag or something like that. It would be interesting to know if the reporter was using 7 with lots of the pretty bits enabled and other things running when this occurs. Certianly in XP these conditions seem to make it occur far more often. Also of course is it possible that something else is coming along and cancelling the read before it starts? I wonder which synth is in use. Its far worse for me with Sapi 5 which suggests its due to processor loading or general congestion in the machine.

@nvaccessAuto
Copy link
Author

Comment 5 by mdcurran on 2011-06-24 04:44
Fixed for Office 2010 in f370813. Please reopen if this problem is actually seen again in older office versions. Note that the UAC problem was also fixed in 1bc2ae5.
Changes:
Milestone changed from None to 2011.2
State: closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant