microsoft / microsoft/BotFramework-WebChat

Unnecessary Document information is announced upon focusing on Bot response message.

Open
#5,016 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

area-accessibility Bot Services bug customer-reported
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.

What is the PWD impact?

Visually challenged users who rely on screen readers will be impacted if Unnecessary Document information is announced upon focusing on Bot response message.

What browsers and screen readers do this issue affect?

Others

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?

Others or unrelated

What is the public URL for the website?

https://airtuserexpdev.azurewebsites.net/Dashboard

How to reproduce the issue?

Step 1: Open the above URL in Edge Browser.

Step 2: AIRT Dashboard page will appear, Navigate to “Chat with Sage” chat box at the bottom of the page.

Step 3: Enable NVDA and Navigate to Bot response message.

Step 4:Verify whether unnecessary document information is announced upon focusing on Bot response message or not.

What do you expect?

Unnecessary Document information should not be announced upon focusing on Bot response message.
NVDA expected response: "Chat History, bot said "Message."

What actually happened?

Unnecessary Document information is announced upon focusing on Bot response message.
Observation: NVDA announcing as "Chat History, document 1 of 1, bot said "Message".

Do you have any screenshots or recordings to repro the issue?

MAS 1 3 1_Unneccesary Document info announced'

Did you find any DOM elements that might have caused the issue?

No response

MAS reference

https://microsoft.sharepoint.com/:w:/s/accessibility/EXdDUZzldv5MgwDaMHnTzcMBcT8opKGncYjU-gCJ4uqQdg?e=9nuVmt

WCAG reference

No response

WAI-ARIA reference

No response

Adaptive Card JSON

No response

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 by reproducing the bot response focus behavior at the provided AIRT Dashboard URL in Edge with NVDA, then inspect the Web Chat bot response entry point and its accessibility announcements. Done means focusing the response announces only “Chat History, bot said ‘Message’,” without “document 1 of 1.”

Written by the indexing model from the issue text.

Assessment

Tech stack
html
Domain
accessibility, frontend, web-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
40/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.