[Adaptive Cards- Expenses Report]: While navigating on the 'Expand' button, screen reader is not conveying descriptive information. #9023
Labels
A11yCT
For CT Test Pass
A11ySev3
Accessibility issue with severity 3
A11yWCAG
Accessibility issue that affects compliance
Area-Accessibility
Bugs around feature accessibility
Area-Renderers
Bug
HCL-AdaptiveCards-Web
Used by accessibility team for scorecard categorization
HCL-E+D
Product-AC
Target Platforms
Other
SDK Version
1.6
Application Name
Adaptive Cards
Problem Description
Test Environment:
URL: https://adaptivecards.io/
OS Version: Dev (OS Build 27695.1000)
Browser Version: Version 130.0.2849.1 (Official build) dev (64-bit)
Screen Reader: Narrator
Pre-Requisite:
Turn on screen reader using caps + spacebar key.
Repro steps:
Actual Result:
While navigating on the expand button present on the expenses report screen reader is not conveying descriptive information as category is not associated with the button. It is announcing only as 'Expand button.'
Also, after activating the expand button, screen reader is not announcing the changed state as it is only announcing as expand button.
Expected Result:
Screen reader should announce the descriptive information while navigating on the expand button. It should announce as 'Expand Air Travel expenses button.'
Also, when user activates expand button it should announce as expanded.
Note:
Same issue is repro with NVDA as well.
User Impact:
It will impact the screen reader user as they will not be able to know descriptive information about the expand button also there are 3 expand buttons are present so user will get confused if the screen reader will announce the same information for the all buttons,
WCAG Reference:
https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships
Have feedback to share on Bugs ? please tag bug as “A11yRCA” and add your feedback in the comment section
Screenshots
While.navigating.on.the.Expand.button.screen.reader.is.not.conveying.descriptive.information.mp4
Card JSON
NA
Sample Code Language
No response
Sample Code
No response
The text was updated successfully, but these errors were encountered: