microsoft / microsoft/BotFramework-WebChat
[COGNITION]: The chat messages should not have screen reader only information between the end of chat message and text input
@compulim is already working on this.
Since Oct 29, 2022.
- Dominant language
- HTML
- Stars
- 1.8k
- Forks
- 1.6k
- Avg merge
- 22h 58m
- Merged PRs (30d)
- 2
Description
Please view our Technical Support Guide before filing a new issue.
Screenshots

Version
<meta name="botframework-directlinespeech:version" content="4.12.0">
<meta name="botframework-webchat:bundle:variant" content="full-es5">
<meta name="botframework-webchat:bundle:version" content="4.12.0">
<meta name="botframework-webchat:core:version" content="4.12.0">
<meta name="botframework-webchat:ui:version" content="4.12.0">
Describe the bug
As a screen reader user, I want to be able to hear the end of the transcript message, then the input to ask another question immediately after. There's a lot of information before the text input that was confusing and didn't feel actionable.
Steps to reproduce
There's several pieces of information being read out after I listen to the "End of chat" message before I can ask a new question when I'm using a screen reader. Specifically the following 4 pieces of information are read aloud:
Connectivity Status: Connected
Suggested Actions Container: Is empty, application status
Suggested Actions Container: Is empty
End of, Suggested Actions Container: Is empty, application status
Ideally these would be removed or hidden from screen readers unless they are important for the user experience.
Expected behavior
- Details of the ticket are considered by the development team and text is hidden from assistive technology OR
- Messages are updated to be meaningful or give users more context about what they are supposed to do
Additional context
Corresponds to this VA GitHub issue: https://github.com/department-of-veterans-affairs/va.gov-team/issues/25183
[Bug]
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.
Assessment
This issue has not been assessed yet.