{Freeway-Bug}[Adaptive Cards> Expenses Report]: No name is defined for the 'Show History' button.

[vagpt]

Target Platforms

UWP

SDK Version

1.0.1.0

Application Name

Adaptive Cards

Problem Description

Test Environment:
Application: Adaptive Cards Universal
OS Build: 24H2 (OS Build 26252.5000)
App Version: 1.0.1.0
Screen Reader: Narrator

Repro Steps:

1. Open the Adaptive Cards Universal application.
2. Adaptive Card UWP Visualizer screen starts appearing.
3. Navigate to Expenses Report.Json button by using Tab key and activate it.
4. Expenses Report adaptive card will appear on right sight of the pane.
5. Navigate to Expenses Report card by using Tab key.
6. Press the tab key and navigate to the 'Show History' button and observe the issue.

Actual Result:
While navigating the expenses report card, screen reader is not conveying the name of the 'Show History' 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 'Show History' button screen reader is not conveying the changed name information. It is remain silent.

Expected Result
Name should be defined for the Show History button so that when the screen reader focus lands on it then it should announce the information as 'Show History button.'
Also, when user activates show history button then it should announce as 'Hide History' and vice versa.

Note:
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

No.name.is.defined.for.the.Show.History.button.mp4

Card JSON

NA

Sample Code Language

No response

Sample Code

No response

[vagpt]

This issue is still repro, hence we will reactivate this bug in next month first week.

Build Version:
1.0.2.0

Snippet:

[vagpt]

Now this issue is being tracking with below bug URL hence closing this issue.

#9076