microsoft / microsoft/BotFramework-WebChat
[Fluent UI -Suggested actions]: Keyboard focus is not visible on 'Previous and Next' icons while navigating with tab 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 response
What is the PWD impact?
Keyboard‑only users may not know which control currently has focus. This makes it difficult to navigate the interface, interact with controls confidently, and complete actions efficiently. Users with low vision or motor disabilities are especially impacted.
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 navigation
What is the public URL for the website?
No response
How to reproduce the issue?
Repro Steps
- 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 Fluent UI experience chat page and type Suggested-actions word in type your message text box. - Response will appear.
- Navigate to the Next and Previous control.
- Observe an issue that Keyboard focus is not visible on 'Previous and Next' icons while navigating with tab key.
What do you expect?
The element should provide a clear, visible focus indicator when navigated to using the keyboard.
What actually happened?
Keyboard focus is not visible on 'Previous and Next' icons while navigating with tab key.
Do you have any screenshots or recordings to repro the issue?
https://github.com/user-attachments/assets/0d9b6381-396f-4a58-8c10-ecb013358a87
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 with the Fluent UI experience in the Web Chat loader URL and reproduce the issue by tabbing to the Suggested actions Previous and Next controls. Inspect those controls while using Edge and Windows Narrator, then verify that both show a clear visible keyboard-focus indicator when the issue is fixed.
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
- 48/100