-
-
Notifications
You must be signed in to change notification settings - Fork 784
Contents of comments in Word 365 with NVDA+alt+c or elements list. #14985
Copy link
Copy link
Open
Labels
app/microsoft-officecomponent/UIA-ms-officeSpecific to UIA used in MS office applications.Specific to UIA used in MS office applications.p3https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#prioritytriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Metadata
Metadata
Assignees
Labels
app/microsoft-officecomponent/UIA-ms-officeSpecific to UIA used in MS office applications.Specific to UIA used in MS office applications.p3https://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#priorityhttps://github.com/nvaccess/nvda/blob/master/projectDocs/issues/triage.md#prioritytriagedHas been triaged, issue is waiting for implementation.Has been triaged, issue is waiting for implementation.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Steps to reproduce:
Actual behavior:
Using both NVDA+alt+c and the elements list, NVDA reads the user who added the comment and the time the comment was added:
Comment: Comment thread started by Quentin Christensen by Quentin Christensen on 08 June 2023, 9:58 AM
But the actual text of the comment is not read.
Expected behavior:
NVDA should first read the text of the comment, and then read any associated info such as who left the comment and when.
NVDA logs, crash dumps and other attachments:
System configuration
NVDA installed/portable/running from source:
NVDA version:
NVDA 2023.1 installed
Windows version:
Windows 11 (64-bit) Version: 22H2, Build: 22621.1778
Name and version of other software in use when reproducing the issue:
Office 365 (64-bit) Version: 16.0.16327.20248
Other information about your system:
Other questions
Does the issue still occur after restarting your computer?
Have you tried any other versions of NVDA? If so, please report their behaviors.
If NVDA add-ons are disabled, is your problem still occurring?
Does the issue still occur after you run the COM Registration Fixing Tool in NVDA's tools menu?