microsoft / microsoft/BotFramework-WebChat
Screen reader is announcing questions as toggle button off for every question which is confusing to the screen reader users.
Nobody has claimed this yet.
- 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?
Screen reader users will be confused on interacting with the questions if they are being announced as toggle buttons.
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?
Others or unrelated
What is the public URL for the website?
https://servicesuat.microsoft.com/#/opdashboard/
How to reproduce the issue?
- Hit the URL https://servicesuat.microsoft.com/#/opdashboard/
- Tab till iris bot icon in the header section and press enter.
- Iris bit welcome screen will be displayed.
- Tab till top questions for your role and press enter.
- Start Narrator and tab till first question and observe the announcement.
What do you expect?
Screen reader should announce as button as announcing toggle button can be confusing to the screen reader users.
What actually happened?
Screen reader is announcing questions as toggle button off for every question which is confusing to the screen reader users.
Environment Details:
- Application Name: Intelligent Support
- URL:Resource360 Dashboard (microsoft.com)
- Chromium Version:114.0.1823.86 (Official build) (64-bit)
Do you have any screenshots or recordings to repro the issue?
11059099A11y_Intelligent Support_Iris bot_Top questions for your role_ScreenReader.webm
Did you find any DOM elements that might have caused the issue?
No response
MAS reference
MAS 1.3.1 – Info and Relationships
WCAG reference
No response
WAI-ARIA reference
No response
Adaptive Card JSON
No response
Additional context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue at the provided Resource360 Dashboard URL using Edge with Windows Narrator, then inspect how the top-question controls are exposed to assistive technology. The issue names no source files or tests; done means each question is announced as a button rather than a toggle button, with the behavior verified against the reported reproduction steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100