Is it an issue related to Adaptive Cards?
No.
What is the PWD impact?
Screen reader users cannot identify who authored a message or when it was sent while reviewing chat history. This removes important conversational context and makes it difficult to understand discussion flow, follow message chronology, and participate independently in conversations.
What browsers and screen readers do this issue affect?
Windows: Edge with Windows Narrator
Are there any code-based customization done to Web Chat?
No, I am using Web Chat without any customizations except "styleOptions".
What version of Web Chat are you using?
Latest production
Which area does this issue affect?
ARIA roles
What is the public URL for the website?
https://msft-lcw-trial.azureedge.net/elopez/A11Y/testing/demo-oauth.html
How to reproduce the issue?
Open the test URL in Microsoft Edge and sign in using a valid V- account.
Turn on Narrator and ensure Scan Mode is turned off.
Navigate to the "Let's chat" button using the Tab key and activate it using Enter.
Move focus to the chat panel, navigate to the chat area, and press Enter.
Use the Up Arrow and Down Arrow keys to navigate through chat messages and observe the information announced by Narrator.
What do you expect?
The chat message element should expose the sender name, date, and time programmatically so that Narrator announces this information along with the message content when users navigate through the chat history.
What actually happened?
While navigating through chat messages, Narrator announces the message content but does not announce associated contextual information such as the sender's name, message date, or message time. As a result, users are unable to determine who sent the message and when it was posted.
Do you have any screenshots or recordings to repro the issue?
No response
Did you find any DOM elements that might have caused the issue?
No response
MAS reference
https://learn.microsoft.com/accessibility/standards/web/requirements#412-name-role-value
WCAG reference
No response
WAI-ARIA reference
No response
Adaptive Card JSON
Additional context
Is it an issue related to Adaptive Cards?
No.
What is the PWD impact?
Screen reader users cannot identify who authored a message or when it was sent while reviewing chat history. This removes important conversational context and makes it difficult to understand discussion flow, follow message chronology, and participate independently in conversations.
What browsers and screen readers do this issue affect?
Windows: Edge with Windows Narrator
Are there any code-based customization done to Web Chat?
No, I am using Web Chat without any customizations except "styleOptions".
What version of Web Chat are you using?
Latest production
Which area does this issue affect?
ARIA roles
What is the public URL for the website?
https://msft-lcw-trial.azureedge.net/elopez/A11Y/testing/demo-oauth.html
How to reproduce the issue?
Open the test URL in Microsoft Edge and sign in using a valid V- account.
Turn on Narrator and ensure Scan Mode is turned off.
Navigate to the "Let's chat" button using the Tab key and activate it using Enter.
Move focus to the chat panel, navigate to the chat area, and press Enter.
Use the Up Arrow and Down Arrow keys to navigate through chat messages and observe the information announced by Narrator.
What do you expect?
The chat message element should expose the sender name, date, and time programmatically so that Narrator announces this information along with the message content when users navigate through the chat history.
What actually happened?
While navigating through chat messages, Narrator announces the message content but does not announce associated contextual information such as the sender's name, message date, or message time. As a result, users are unable to determine who sent the message and when it was posted.
Do you have any screenshots or recordings to repro the issue?
No response
Did you find any DOM elements that might have caused the issue?
No response
MAS reference
https://learn.microsoft.com/accessibility/standards/web/requirements#412-name-role-value
WCAG reference
No response
WAI-ARIA reference
No response
Adaptive Card JSON
Additional context