Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Make UIA in MS Word optional again, through an Advanced Settings category #9200
Link to issue number:
Summary of the issue:
NVDA switched to using UI Automation to access Microsoft Word document controls by default for Office 2016/365, however Office's UIA support is still not 100% complete.
Description of how this pull request fixes the issue:
UIA is no longer used by default in MS Word. However, there is now a new Advanced Settings category in NVDA's settings dialog which contains a checkbox to turn this on for testing this feature out.
Tested each option in the Advanced settings category to ensure that their setting is remembered when opening the Settings dialog again, and that the option is truly activated / deactivated in NVDA itself.
Known issues with pull request:
Although there is a panel caption warning the user to be careful with these settings, it is not automatically read by NVDA when tabbing from the categories list into the settings themselves. This is similar to the Document Formatting settings caption which is also not read.
Change log entry:
referenced this pull request
Jan 27, 2019
@leonardder: That's right, but the user should be able to control and understand the developer's choice. In the end he always can (and should) read the log file before sending/uploading it. So updating this wiki article should be enough.
I'm not sure if the User Guide contains links to wiki articles. If not, then the User Guide is already okay.
Edit: And maybe parts of the wiki article Log Files and Crash Dumps should be updated too.
@feerrenrut If we did what you proposed, this would be a change to the current behaviour in 2018.4. Enabling the option allows UIA to work in MS Word where ever it is implemented. Which happens to be Office 2016. True that the UIA implementation pre build 9000 had some bugs, it was still quite usable. Note also that even in master right now, if that option is manually enabled, the version check is overridden and it will work for all of Office 2016 builds. I would prefer to keep it as is for now, as it is much easier for users to understand "I have Office 2016" rather than "I have Office 2016 post build 9000".