BotFramework-WebChat
BotFramework-WebChat copied to clipboard
microsoft
Screen reader is announcing questions as toggle button off for every question which is confusing to the screen reader users.
Is it an issue related to Adaptive Cards?
No.
What is the PWD impact?
Screen reader users will be confused on interacting with the questions if they are being announced as toggle buttons.
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?
https://servicesuat.microsoft.com/#/opdashboard/
How to reproduce the issue?
- Hit the URL https://servicesuat.microsoft.com/#/opdashboard/
- Tab till iris bot icon in the header section and press enter.
- Iris bit welcome screen will be displayed.
- Tab till top questions for your role and press enter.
- Start Narrator and tab till first question and observe the announcement.
What do you expect?
Screen reader should announce as button as announcing toggle button can be confusing to the screen reader users.
What actually happened?
Screen reader is announcing questions as toggle button off for every question which is confusing to the screen reader users.
Environment Details:
- Application Name: Intelligent Support
- URL:Resource360 Dashboard (microsoft.com)
- Chromium Version:114.0.1823.86 (Official build) (64-bit)
Do you have any screenshots or recordings to repro the issue?
11059099A11y_Intelligent Support_Iris bot_Top questions for your role_ScreenReader.webm
Did you find any DOM elements that might have caused the issue?
No response
MAS reference
MAS 1.3.1 – Info and Relationships
WCAG reference
No response
WAI-ARIA reference
No response
Adaptive Card JSON
No response
Additional context
No response
#A11yMAS;#A11ySev3;#MAS1.3.1;#HCL;#Accessibility;#FeatureBotframeworkwebchat-Apr23;
This is by design.
Adaptive Cards supports repetitive submissions. In other words, after a button is clicked, the user can go back and click another button. This is the design of Adaptive Cards.
Thus, multiple choices requires us to use a push button approach via aria-pressed="true" to indicate what button is selected.
If repetitive submission is not desirable, the customer should consider using suggested actions, instead of Adaptive Cards.
HI @compulim Thanks for sharing details on this with your justification to mark it as By Design. I discussed this issue with SMEs and per their feedback, this does not sound like an accessibility issue. But this should be documented in Bot Framework Webchat docs on how these button works and what is the purpose of functionality on these buttons.