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 no longer reads the elements in the ribbons in Word 2013 #5504
Comments
This is the log file that I was able to get for this problem. INFO - main (12:40:16): DEBUGWARNING - watchdog.watcher (12:40:26): DEBUGWARNING - eventHandler.executeEvent (12:40:26): |
Same comments apply as #5546: I can't reproduce this. It's as if this information just never gets to NVDA, which is very odd. Have you tried restarting NVDA with all add-ons disabled? |
Yes I have, and I also tried uninstalling all office updates. I remember that this was a problem in one of the 2013 versions of NVDA, and a ticket was filed, and even thow the problem was fixed it was never closed. |
Sorry it was a 2014 version the ticket is #4683 |
It seems this happens when the ribbon is collapsed/minimised, but not when it is expanded. The workaround for now is to expand the ribbon by pressing control+f1. This does not happen in Word 2010, but does in both 2013 and 2016. Technical: Brief testing shows this is definitely due to an event being blocked by eventHandler.shouldAcceptEvents. Regression possibly introduced by 46f53f9 or b0eceb5. |
Ok will keep a tab on this. El 21/12/2015 a las 11:44 p.m., James Teh escribió:
|
…ly tabs, items in the ribbon are again reported as expected when a tab is activated. Fixes #5504.
Incubated in d849aa5. |
Hi,
Since the versions of NVDA after 2015.3, NVDA does not read the elements in the ribbons in word 2013. For example it reads the names of the ribbons but when they are open it does not read the options, also the ribbons are not red when using the shortcut keys. However it reads the ribbons fine in the other office 2013 applications.
I do not have this problem when using JAWS nor Window eyes.
I am using Windows 7 Ultimate 64 bits.
The text was updated successfully, but these errors were encountered: