You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Make sure it has some context changing things such as a table, or heading, or the like.
Now press NVDA+Space.
Move the cursor with down arrow. Result: NVDA will repeat the last context change, for example, by announcing the page number.
Navigate around to a different item such as a heading or table cell.
Press NVDA+Space again to turn off browse mode.
Move the cursor. Result: Again, NVDA will repeat the last context change, e. g. speak the entering into the table.
I think this double announcement of the context should be suppressed. Since the actual Word caret moves along anyway when navigating in browse mode, and the browse mode cursor likewise when editing a document, double-speaking the context change is superfluous. It would be more polished if the switching was just seamless and one can continue working without being distracted by this extra context announcement that one already knows about.
The text was updated successfully, but these errors were encountered:
Confirmed in Word 2010 using NVDA 2017.3. When pressing NVDA+Space while browsing Word documents for my school textbook's soft copies, NVDA unnecessarily reports the page number, which can get slightly annoying and obtrusive when focus and browse mode are both required for productivity purposes. CC @michaelDCurran (Microsoft Office expert)
I am not reproducing this issue with NVDA 2019.1.1, Word 2010 and Word 2016 / 365. Closing as works for me. @MarcoZehe if you are still having this problem, please feel free to comment on it and we can reopen the discussion. Thanks.
Reported by MarcoZehe on 2015-01-27 14:00
Steps:
I think this double announcement of the context should be suppressed. Since the actual Word caret moves along anyway when navigating in browse mode, and the browse mode cursor likewise when editing a document, double-speaking the context change is superfluous. It would be more polished if the switching was just seamless and one can continue working without being distracted by this extra context announcement that one already knows about.
The text was updated successfully, but these errors were encountered: