microsoft / microsoft/BotFramework-WebChat
A11y_ScreenReader: Screen Readers (NVDA/JAWS) focus is not going over the chat, present in the chat bot in scan mode using up/down arrow key.
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?
Users who are dependent on-screen readers will find difficulty while navigating over the chat present in the chat bot.
What browsers and screen readers do this issue affect?
Windows: Chrome with NVDA
Are there any code-based customization done to Web Chat?
Yes, however, this also repro when customizations are not in use.
What version of Web Chat are you using?
Latest production
Which area does this issue affect?
Transcript navigation
What is the public URL for the website?
No response
How to reproduce the issue?
just launch a LCW widget , is expected that all the information displayed as part of the chat window is part of the information narrated by screen reader
What do you expect?
Screen Readers (NVDA/JAWS) focus should go over the chat in scan mode using up/down arrow key.
What actually happened?
Screen Readers (NVDA/JAWS) focus is not going over the chat in scan mode using up/down arrow key.
If focus goes inside the chat bot, screen reader should announce complete information of the chat including name and time of the chat.
For example: hi 6:42 PM - sent like that
Do you have any screenshots or recordings to repro the issue?
Did you find any DOM elements that might have caused the issue?
The span with the time stamps info and user name is not reachable and somehow is not visible for the screen reader
MAS reference
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
Start by launching an LCW widget in Chrome with NVDA and reproducing transcript navigation in scan mode. Inspect the transcript DOM, especially the spans containing timestamps and user names; done means arrow-key navigation reaches each chat message and the screen reader announces its complete information, including name and time.
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
- 35/100