microsoft / microsoft/BotFramework-WebChat
"Send" button is missing sufficient labeling
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?
No response
What browsers and screen readers do this issue affect?
No response
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?
ARIA roles, Send box
What is the public URL for the website?
How to reproduce the issue?
This is feedback from the accessibility company Allyant who has been testing our website and has people who use screenreaders and other assistive technologies as a part of their testing team.
What do you expect?
Add screen reader only text or an aria-label attribute to each button which tells users where it goes and/or what it does.
What actually happened?
The send button only has a title attribute. The title attribute is not sufficient for button labeling.
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
No response
WCAG reference
https://www.w3.org/WAI/WCAG22/Understanding/info-and-relationships; https://www.w3.org/WAI/WCAG22/Understanding/headings-and-labels
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
Start at the Web Chat Send box and inspect the rendered Send button, especially its title attribute and accessible name. Confirm the button exposes a useful label to screen readers, then verify the result with an accessibility inspection or screen reader; done means the button is announced with its purpose rather than only its title.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100