microsoft
Buttons options function as a list and should be indicated as such to screen reader users.
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.
What do you expect?
When a series of similar items is grouped together in a meaningful or deliberate way, this should be conveyed to screen reader users. Use standard HTML to mark up all such content as a list.
What actually happened?
The buttons are not conveyed as a list to screen reader users.
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/info-and-relationships
WAI-ARIA reference
No response
Adaptive Card JSON
No response
Additional context
No response
These buttons are grouped as toolbar, https://w3c.github.io/aria/#toolbar. They are grouped and implemented by following this APG pattern, https://www.w3.org/WAI/ARIA/apg/patterns/toolbar/.
Circled in the screenshot, the container has a role of toolbar and is grouping a collection of buttons.
