Arrow navigation is not implemented for the cards. #5743
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 arrow key navigation is not implemented for cards, keyboard users cannot move between cards efficiently. They may be forced to tab through the entire page, which is slow and confusing, especially if each card contains multiple interactive elements.
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 cards.
- Observe the issue that Arrow navigation is not implemented for the cards.
What do you expect?
Arrow navigation should be implemented for the cards.
What actually happened?
Arrow navigation is not implemented for the cards.
Do you have any screenshots or recordings to repro the issue?
Arrow.navigation.is.not.implemented.for.the.cards.mp4
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