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

NVDA does not report that text is "hidden" when show formatting is enabled in Word (365 at least) #8713

Closed
Qchristensen opened this issue Sep 4, 2018 · 0 comments · Fixed by #10313
Milestone

Comments

@Qchristensen
Copy link
Member

@Qchristensen Qchristensen commented Sep 4, 2018

Steps to reproduce:

Open Word, type some text, including hidden text. To hide text, press CONTROL+D to open the font formatting dialog, then press alt+h to toggle the "hidden" effect. Press ENTER to close.

Press CONTROL+SHIFT+8 to toggle show formatting.

Ensure font attributes is checked in NVDA's document formatting settings.

Actual behavior:

With Show formatting enabled the hidden text is visible. NVDA reads it as any other text, but does not report that the text is set to hidden (as it would for bold or underlined text, for instance).

With Show formatting disabled, the text is hidden, there is no visual cue and NVDA reads the document as if the hidden text did not exist (the correct behaviour).

Expected behavior:

With show formatting enabled, NVDA should report that the text is "hidden" just as it would for other font attributes like italic.

With Show formatting disabled, the text is hidden, there is no visual cue and NVDA reads the document as if the hidden text did not exist (the correct behaviour).

System configuration:

Windows 10 Version:
Version 1809 Fast insider 17751.1

Office 365 Version:
16.0.10325.20118

NVDA version:

alpha-15933,b3aff97c Installed
2018.3beta3 portable

Does the issue still occur after restarting your PC?

Yes

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

Successfully merging a pull request may close this issue.

2 participants