microsoft / microsoft/BotFramework-WebChat
Keyboard focus indicator is not visible on the 'Next' and 'Previous' control.
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?
Yes, this is related to Adaptive Card. However, it does not repro on Adaptive Cards Designer.
What is the PWD impact?
When the keyboard focus indicator is not visible on the “Next” and “Previous” controls, keyboard users cannot determine which element currently has focus. This makes navigation unpredictable and prevents users from reliably moving through paginated or carousel content.
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?
No response
How to reproduce the issue?
Repro Steps:
- Open URL: Web Chat in edge browser.
- Ask query 'Carousel'.
- Navigate to next and previous control.
- Observe the issue that Keyboard focus indicator is not visible on the 'next' and 'previous' control.
What do you expect?
Keyboard focus indicator should be visible on the 'next' and 'previous' control.
What actually happened?
Keyboard focus indicator is not visible on the 'next' and 'previous' control.
Do you have any screenshots or recordings to repro the issue?
https://github.com/user-attachments/assets/67f1116a-5141-4509-8833-b9a4211db1f1
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/WCAG21/Understanding/focus-visible
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 carousel scenario in Edge with Windows Narrator, then inspect the Next and Previous controls in the Web Chat UI. Done means keyboard users can clearly see which control has focus while navigating carousel content, with behavior checked against the linked focus-visible guidance.
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
- 42/100