microsoft / microsoft/BotFramework-WebChat
[White-label -Video Vimeo]: Translate audio control which is present under video is not keyboard accessible.
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 rely on keyboard navigation (Tab, Shift+Tab, Enter, Space) cannot reach or activate the control. This includes users with motor disabilities and users who cannot operate a mouse.
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?
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 Video vimeo word in type your message text box.
4.Video vimeo will appear. - Observe that "Translate audio" control is keyboard accessible.
What do you expect?
The “Translate audio” control is fully keyboard accessible, meaning it can be reached using the Tab key, clearly receives visible focus, and can be activated using standard keyboard keys (Enter/Space). All associated options (e.g., language selection) are also operable via keyboard and properly exposed to assistive technologies.
What actually happened?
"Translate Audio" control which is present under video is not keyboard accessible. Here we used tab, Shift+Tab, UP/Down arrow key.
Do you have any screenshots or recordings to repro the issue?
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/keyboard
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 at the provided Web Chat URL and navigating to the Vimeo video as described. Inspect the “Translate audio” control and its language options while using Tab, Shift+Tab, Enter, Space, and arrow keys. Done means the control and associated options receive visible focus, are keyboard operable, and are exposed correctly to assistive technologies.
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
- Needs clarification
- Newbie friendliness
- 35/100