microsoft / microsoft/BotFramework-WebChat

Screen reader in mode scan-off doesnt include all info displayed

Open
#5,617 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A11ySev3 A11yWCAG Accessibility area-accessibility Bot Services BotFrameworkWebChat_Web bug customer-replied-to customer-reported HCL-BIC
Dominant language
HTML
Stars
1.8k
Forks
1.6k
Avg merge
22h 58m
Merged PRs (30d)
2

Description

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"

Image

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 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

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the full-bundle demo URL and reproduce the issue in Windows Edge with Narrator, scan mode off. Inspect the transcript navigation and the webchat__stacked-layout__status element while moving across messages. Done means the message and its status information, such as the sender and elapsed time, are included in the screen reader narration.

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
accessibility, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.