microsoft / microsoft/BotFramework-WebChat
[White Label - Layout Carousal]: Keyboard focus indicator is not visible on "previous" and "next" button.
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?
Without a visible keyboard focus indicator on the “Previous” and “Next” buttons, keyboard-only users cannot determine which element is currently selected, making navigation confusing and potentially preventing task completion.
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?
Keyboard focus indicator
What is the public URL for the website?
No response
How to reproduce the issue?
- Open URL: https://compulim.github.io/webchat-loader/ and sign in using valid credentials.
- Navigate to web chat page and select 4.18.1-main.20240927.ea7a875 (30/9/2024) version and then select mockBot link under present label and then select open web chat in new window link at bottom.
3.Navigate to white label experience chat page and type Layout carousel word in type your message text box.
4.Navigate on the result on "previous" and "next".
5.Observe that Keyboard focus indicator is not visible on "previous" and "next" button.
What do you expect?
The “Previous” and “Next” buttons should display a visible keyboard focus indicator when selected, allowing keyboard-only users to clearly see which element is active during navigation.
What actually happened?
Keyboard focus indicator is not visible on "previous" and "next" button.
Do you have any screenshots or recordings to repro the issue?
https://github.com/user-attachments/assets/1e28e3dc-07a4-4d5d-9550-e3a2405ff92a
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 issue through the linked Web Chat loader, using the white label experience and Layout carousel with keyboard navigation. Inspect the Previous and Next buttons and verify the completed change in Edge with Windows Narrator by confirming that the focused button has a visible indicator.
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
- 45/100