Open Qchristensen opened 5 years ago
Small update on this one I forgot to include originally - Narrator is able to read protected files. So it's likely a regression on our part.
Update: You now don't have to use OCR on the presentation when you run it, but it still only reads when you run the presentation (press F5) rather than when it first opens in what would be edit mode.
Clicking in a slide will allow navigation and reading of the slides, in my experience.
Using:
NVDA 2020.3
Windows 10 (64-bit) Version: 2004, Build: 19041
Office 365 (64-bit) Version: 16.0.13328.20130
If I physically click on a placeholder on a slide in a protected presentation, the focus moves to it, and I can tab between placeholders on the slide as normal, however NVDA does not read anything for me.
Steps to reproduce:
Actual behavior:
Reading the current line reads "Blank". Reading from the current point onwards reads nothing. Pressing arrow keys moves between slides without reading anything. Review cursor / object navigation cannot find the content.
Expected behavior:
The user should be able to read the content to determine whether the file is expected before unprotecting it.
System configuration
NVDA installed/portable/running from source:
NVDA version:
NVDA 2019.2 installed
Windows version:
Windows 10 Version: 18362.1
Name and version of other software in use when reproducing the issue:
Office 365 Version: 16.0.11901.20204
Other information about your system:
Other questions
Does the issue still occur after restarting your PC?
Yes
Have you tried any other versions of NVDA? If so, please report their behaviors.
NVDA back to 2018.2.1 acts the same.
One workaround for anyone experiencing this is to run the slideshow - Press F5, then use NVDA's OCR function (or add-on) to read the content of each slide (the reason I suggest running the slideshow is then you only get the content of the slide, not the rest of the window content such as titles / ruler marks etc)
Note this issue previously existed (and was fixed) in Office 2010 with NVDA 2013.1 as per #3007. I do not know whether this is a new regression in Ofice 365 or whether it currently affects earlier versions of Office.