microsoft / microsoft/AdaptiveCards
{Adaptive Cards - Expense Report}: Screen Reader is not conveying the Required information when navigating to the Please specify an appropriate reason for rejection * edit field..
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:
OS: Win11
OS Version: 24H2 (OS Build 22631.5189)
URL: https://adaptivecards.io/
Edge dev Browser version: 137.0.3255.0 (Official build) dev (64-bit)
Screen Reader: Narrator
Repro Steps:
- Open the above URL on edge dev browser.
- Home page will appear.
- Press tab key and navigate to the Sample tab item and select it.
- Press tab key and navigate to the 'Expense Report' option and press enter key to activate it.
- Press tab key and navigate to the 'Reject' button and press enter key to activate it.
- Navigate to edit field and observe the issue.
Actual Result:
Screen Reader is not announcing the required information while navigating on the Please specify an appropriate reason for rejection edit field here it is announcing as 'Please specify an appropriate reason for rejection edit field.'
Expected Result:
While navigating on the 'Please specify an appropriate reason for rejection ' edit field screen reader should convey the required information as well and it should announce as 'Please specify an appropriate reason for rejection Edit field required.'
Note:
Same issue is repro with NVDA.
User Impact:
It will impact screen reader user as they will not be able to know whether the edit field is required or not?
WCAG Reference:
https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships
Screenshots
https://github.com/user-attachments/assets/66b535bc-f6ac-495f-9e05-0c03426a9a3d
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
Start at the Expense Report sample on adaptivecards.io and reproduce the rejection flow with Narrator or NVDA. Inspect how the required edit field is represented and announced by the sample, then verify that its required state is conveyed when focus reaches it.
Written by the indexing model from the issue text.
Assessment
- Domain
- accessibility
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100