You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Now navigate to "SSO button" , OAuth Button" , "Loop SSO" controls.
Observe that the incorrect role is defined for controls above controls as list item.
Actual Results:
Incorrect role is defined for controls present on adaptive cards as list item instead of button. Screen reader is announcing it as "Loop SSO 3 of 5" for the third button with title "Loop SSO"
Expected Results:
Correct role should be defined as button for the controls present on Adaptive card.
User Impact:
Screen reader user will face difficulties while accessing the control if incorrect role is defined for the control they might confused about the controls.
baton17
changed the title
[Teams ]: Incorrect role is defined for controls present on adaptive cards as list item instead of button.
[Teams]: Incorrect role is defined for controls present on adaptive cards as list item instead of button.
Sep 6, 2022
baton17
changed the title
[Teams]: Incorrect role is defined for controls present on adaptive cards as list item instead of button.
Incorrect role is defined for controls present on adaptive cards as list item instead of button.
Sep 6, 2022
Target Platforms
NodeJS
SDK Version
2.10.0
Application Name
Microsoft Teams
Problem Description
Repro Steps:
Actual Results:
Incorrect role is defined for controls present on adaptive cards as list item instead of button. Screen reader is announcing it as "Loop SSO 3 of 5" for the third button with title "Loop SSO"
Expected Results:
Correct role should be defined as button for the controls present on Adaptive card.
User Impact:
Screen reader user will face difficulties while accessing the control if incorrect role is defined for the control they might confused about the controls.
Screenshots
No response
Card JSON
Sample Code Language
No response
Sample Code
No response
The text was updated successfully, but these errors were encountered: