microsoft / microsoft/AdaptiveCards
{Linked:Bug15457038}[Adaptive Cards > Designer]: NVDA is not announcing the whole information present in the Comment 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:
URL: https://adaptivecards.io/samples/InputsWithValidation.html
OS Version: 25H2 (OS Build 26200.5761)
Browser Version: Version 145.0.3734.1 (Official build) dev (64-bit)
Screen Reader: NVDA
Repro Steps:
- Turn on NVDA..
- Open the above URL on the Edge Dev browser.
- Navigate to the 'Sample' control present on the header section of the page using tab key and activate using enter key.
- Navigate to the Inputs with Validation control and activate it.
- Press tab key and navigate to the 'Comment' edit field under Input,text element section and observe the issue.
Actual Result:
While navigating to the comment edit field, screen reader is not announcing the multiple line information. Here, it is announcing as 'Comment edit enter any comment test line 1.'
Note:
Same issue is working fine with Narrator.
Expected Result:
NVDA should announce the whole information present in the Comment edit field and it should announce as 'Comment edit field test line 1 test line 2 test line 3'
User Experience:
Users who rely on screen reader for navigation will be impacted if NVDA is not announcing the whole information present in the Description edit field.
WCAG Reference:
https://www.w3.org/WAI/WCAG22/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/d80a6dea-49e9-402e-bcc6-1d62ad1a81b2
Card JSON
NA
Sample Code Language
No response
Sample Code
Originally tracking with https://microsoftit.visualstudio.com/OneITVSO/_workitems/edit/15457038
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 by reproducing the issue at the InputsWithValidation sample URL with Edge Dev and NVDA, then inspect the Comment edit field and its multiline content. Determine whether the missing announcement is caused by the sample or by browser and screen-reader behavior; done means NVDA announces the complete information as described in the expected result.
Written by the indexing model from the issue text.
Assessment
- Domain
- accessibility, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100