microsoft
Screen reader in mode scan-off doesnt include all info displayed
Is it an issue related to Adaptive Cards?
No response
What is the PWD impact?
This is a mirror bug created for LCW, I was able to reproduce using https://microsoft.github.io/BotFramework-WebChat/01.getting-started/a.full-bundle/
When user navigates across messages , with scren reader on and scan mode off, the narrator does not mention the information in webchat__stacked-layout__status
for the case attached the text missing as part of the narration is "28 miinutes ago"
User Impact: Users relying on Screen Readers cannot identify who sent the message or when it was sent.
MAS Reference: MAS 4.1.2 – Name, Role, Value
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?
Transcript navigation
What is the public URL for the website?
No response
How to reproduce the issue?
- screen reader on
- scan mode off
- go to https://microsoft.github.io/BotFramework-WebChat/01.getting-started/a.full-bundle/
- exchange messages
- navigate across messages
Screen reader only includes the message but not the content of the status (30 minutes ago by example)
What do you expect?
all information should be announced by Screen Reader while navigating in chat section.
What actually happened?
Only the message is part of the screen reader narration
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://www.w3.org/WAI/WCAG21/Understanding/name-role-value.html
WCAG reference
No response
WAI-ARIA reference
No response
Adaptive Card JSON
Additional context
No response
Talked to accessibility team.
- Screen reader should read relative timestamp (as what is on the screen), not absolute timestamp
- It's P3 because there are no data loss, just reading same thing but in different format (relative vs. absolute)
Will fix.
