{Freeway-Bug}[Adaptive Cards> Expenses Report]: Name is not defined for the 'Expand and Collapsed' button present under Amount column. #9076
Labels
A11yRT
For RT Test Pass
A11ySev2
Accessibility issue with severity 2. This may impact the accessibility score
A11yWCAG
Accessibility issue that affects compliance
AdaptiveCards_Universal
a11y tag
Area-Accessibility
Bugs around feature accessibility
Area-Renderers
Bug
HCL-AdaptiveCards-Universal
a11y tag
HCL-E+D
Product-AC
Target Platforms
UWP
SDK Version
1.0.2.0
Application Name
Adaptive Cards
Problem Description
Test Environment:
Application: Adaptive Cards Universal
OS Build: 24H2 (OS Build 26252.5000)
App Version: 1.0.2.0
Screen Reader: Narrator
Repro Steps:
Actual Result:
While navigating the expenses report card, screen reader is not conveying the name of the 'Expand or collapse' button as no name is defined for the same. When the focus lands on it then it is announcing only as 'Button.'
Also, after activating the 'Expand or collapse' button screen reader does not convey the changed name information. It remains silent.
Expected Result:
Name should be defined for the Expand or collapse button so that when the screen reader focus lands on it then it should announce the information as 'Expand Air Travel expenses dollar 300 button.'
Also, when user activates Expand button then it should announce as 'Expanded' and vice versa.
Note:
Same issue is repro with 'Show History' button.
Same issue is repro with NVDA.
User Impact:
This will impact the screen reader user as they will not be able to know the name of the control due to this they will not able to get to know by activating the control what action will be performed.
WCAG Reference:
https://www.w3.org/WAI/WCAG21/Understanding/name-role-value
Have feedback to share on Bugs ? please tag bug as “A11yRCA” and add your feedback in the comment section.
Screenshots
Name.is.not.defined.for.the.Expand.and.Collapsed.button.present.under.Amount.column.mp4
Card JSON
NA
Sample Code Language
No response
Sample Code
Originally tracking with below bug -
#8973
The text was updated successfully, but these errors were encountered: