microsoft / microsoft/BotFramework-WebChat
[White Label-Card Bingsports]: Narrator does not navigate Card controls when using arrow keys.
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?
Screen reader users cannot explore the contents of a card using arrow navigation, forcing them to rely only on Tab. This results in slower, more cumbersome navigation and makes it difficult to understand the logical structure of the 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?
Focus management
What is the public URL for the website?
No response
How to reproduce the issue?
Pre-Requisite:
Turn on Narrator
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 white label experience chat page and type Card Bingsports word in type your message text box. - Response will appear.
- Navigate to the cards in the response.
- Observe an issue that Narrator does not navigate Card controls when using arrow keys.
What do you expect?
The element should expose correct programmatic structure and relationships so Narrator can navigate through the Card controls using arrow keys.
What actually happened?
Narrator does not navigate Card controls when using arrow keys.
Do you have any screenshots or recordings to repro the issue?
No response
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/meaningful-sequence
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 reproduction at the webchat-loader URL, using the specified 4.18.1-main version, Edge, and Windows Narrator. Inspect the card controls and their accessibility tree while testing arrow-key navigation; done means Narrator can move through the card controls in the expected logical sequence.
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
- Needs clarification
- Newbie friendliness
- 35/100