{Linked:Bug13586388}[Adaptive Cards > Designer] - Screen Reader is not conveying the descriptive information while navigating on the 'Book this trip' button. #9163
Labels
A11ySev2
Accessibility issue with severity 2. This may impact the accessibility score
A11yWCAG
Accessibility issue that affects compliance
AdaptiveCards_Web
a11y tag
Area-Accessibility
Bugs around feature accessibility
Area-Renderers
Area-Website
Bug
HCL-AdaptiveCards-Web
Used by accessibility team for scorecard categorization
HCL-E+D
Target Platforms
Other
SDK Version
1.6
Application Name
Adaptive Cards
Problem Description
Test Environment:
URL: https://adaptivecards.io/designer/
OS Version: 24H2 (OS Build 27766.1000)
Browser Version: Version 132.0.2186.2 (Official build) dev (64-bit)
Screen Reader: NVDA
Pre-Requisite:
Run the below attached JSON file under 'Copy Card Payload editor.'
Repro Steps:
Actual Result:
While navigating on the 'Book this trip' button, screen reader is not conveying the descriptive information. Here. it is announcing as 'Book this trip button'.
Expected Result:
Screen Reader should announce the descriptive information while navigating on the 'Book this trip' button for the first button it should announce as '24-7 Test Route AM, Apr 24' Book this trip button' and for second it should announce as '24-7 Test Route AM, Apr 25 Book this trip button'.
Note:
Same issue is repro with Narrator screen reader as well.
User Impact:
It will impact the screen reader user as they will not be able to differentiate between both buttons if the screen reader will not announce the descriptive information. Here user will be confused and not able to know on which button focus is present.
WCAG Reference:
https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships
Have feedback on bugs logged, please tag bug as “A11yRCA” and add your feedback in the comment section.
Screenshots
Screen.Reader.is.not.conveying.the.descriptive.information.while.navigating.on.the.Book.this.trip.button.mp4
Card JSON
Sample Code Language
No response
Sample Code
No response
The text was updated successfully, but these errors were encountered: