microsoft
Negative tabindex attributes on vertical buttons removes them from the tab order
Is it an issue related to Adaptive Cards?
No.
What is the PWD impact?
No response
What browsers and screen readers do this issue affect?
No response
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?
https://edfinancial.com
How to reproduce the issue?
This is feedback from the accessibility company Allyant who has been testing our website and has people who use screenreaders and other assistive technologies as a part of their testing team.
When tabbing through the vertical button options, tabbing takes you out of the button list options and to the input field. The button list can only be navigated with arrow keys. Each element should be focusable by the keyboard when navigating with the Tab and Shift + Tab keys.
What do you expect?
Remove the tabindex attribute from each element so that they can be focused by the keyboard when navigating with the Tab and Shift + Tab keys.
What actually happened?
Currently, tabbing gets you to the button list, but then you have to use up/down arrows to navigate. Tabbing takes you away to the input field.
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/WCAG22/Understanding/keyboard
WAI-ARIA reference
No response
Adaptive Card JSON
No response
Additional context
No response
