microsoft / microsoft/BotFramework-WebChat
Linked:Bug11059109 Screen reader is announcing extra information along with error message
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 if extra information is being read which is not required.
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?
- Turn on Narrator.
- Hit the URL https://servicesuat.microsoft.com/#/opdashboard/
- Tab till iris bot icon in the header section and press enter.
- Iris bot welcome screen will be displayed
- Tab till type your message textbox and type Sap access request.
- Select self and press enter. Form will be displayed.
- Keep the required fields empty.
- Tab till submit button and press enter.
- The error messages will be appeared to the respective required fields.
What do you expect?
Screen reader should read only the displayed error messages of the required field.
What actually happened?
Screen reader is announcing the unnecessary extra information along with the error message appeared for the required field.
Do you have any screenshots or recordings to repro the issue?
Did you find any DOM elements that might have caused the issue?
No response
MAS reference
WCAG reference
https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships.html
WAI-ARIA reference
No response
Adaptive Card JSON
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
Start by reproducing the issue at the provided public URL with Windows Narrator and inspect the required-field error elements in the DOM. Trace how those errors are exposed to the screen reader; done means Narrator announces only the displayed error message for each required field.
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
- 38/100