microsoft / microsoft/AdaptiveCards
[Adaptive Cards- Action.showcard] : 'What do you think' label is not associated with its button control.
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2k
- Forks
- 595
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 1
Description
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
Repro steps:
- Open the above URL in the edge dev browser.
- Navigate to the 'Schema Explorer' option and press enter key to activate it.
- Press tab key and navigate to the 'Action.ShowCard' link and press enter key to activate it.
- Press tab key and navigate to the 'Neat' button and observe the issue.
Actual Result:
While navigating to the 'Neat' button, 'What do you think?' label is not associated with its button control. While navigating on the Neat button screen reader is announcing only as 'Neat button.'
Expected Result:
'What do you think?' label should be associated with button control so that when the screen reader focus lands on it then screen reader should announce the information as 'What do you think? Neat button.'
Note:
- Same issue is repro with NVDA.
- Same issue is repro under Input.Text and column set screen.
- Same issue is repro throughout the application.
User Impact:
It will impact the screen reader user as label is not associated with its controls . User will be confuse about the control like this button related to which area.
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
https://github.com/user-attachments/assets/22e62bf7-c1bd-4e18-b29e-3df444cf8bf7
Card JSON
NA
Sample Code Language
No response
Sample Code
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue at https://adaptivecards.io/ through Schema Explorer and Action.ShowCard, then inspect the implementation used by the Neat button and its surrounding label. Verify the result with Narrator or NVDA, including the Input.Text and column set cases; done means the screen reader announces “What do you think? Neat button.”
Written by the indexing model from the issue text.
Assessment
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100