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

Support Microsoft Outlook 2016 signature editor #7253

michaelDCurran opened this issue Jun 5, 2017 · 0 comments

Support Microsoft Outlook 2016 signature editor #7253

michaelDCurran opened this issue Jun 5, 2017 · 0 comments


Copy link

Steps to reproduce:

With NVDA, open Outlook 2016.
On the ribbon, go to Insert -> Signature -> Signatures...
If needed, create a new Signature.
Once a new or existing signature is active in this dialog, tab to the Signature editor control (one tab stop before the Okay button).
Note that in Outlook 2016, nothing is announced at all.
In previous versions of Office, the control was announced, however arrowing around the control was not always entirely accurate.

Expected results

NVDA should announce the control, and allow reading / editing the content like a normal Microsoft Word document

Technical info:

Office 2016 now provides a native UI Automation implementation for _WwN controls. We should ensure NVDA uses this if available. However, this will involve moving oure existing _WwN support into IAccessible, as it is currently at Window level and will conflict with UIA.

@michaelDCurran michaelDCurran self-assigned this Jun 5, 2017
michaelDCurran added a commit that referenced this issue Jun 16, 2017
…NVDAObjectTextInfos were being classed as navigable. NVDAObjecTextInfo is now never classed as navigable text, and speech also correctly again checks to make sure the reason is not focusEntered.
@nvaccessAuto nvaccessAuto added this to the 2017.3 milestone Jul 18, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet

No branches or pull requests

2 participants