microsoft / microsoft/AdaptiveCards
[Adaptive Cards> InputsWithRTL.json]: Placeholder text is not defined for 'Text input with an inline action with no icon' 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
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
Repro Steps:
- Open the Adaptive Cards Universal application.
- Adaptive Card UWP Visualizer screen starts appearing.
- Navigate to InputFormWithRTL.Json button by using Tab key and activate it.
- InputFormRTL adaptive card will appear on right sight of the pane.
- Navigate to InputFormwithRTL card by using Tab key.
- Press the tab key and navigate to the edit field and observe the issue.
Actual Result:
For 'Name, Edit, Phone and Comments' edit field, there is no placeholder text is defined.
Expected Result
For 'Name, Edit, Phone and Comments' edit field, proper placeholder text should be defined. Such as 'Please enter your name' and so on.
Note:
Same issue repro throughout for all the edit fields.
User Impact:
People with cognitive disability will get impacted as user will not be able to know the purpose of the edit field or will get confused that what type of data needs to enter.
Have feedback to share on Bugs ? please tag bug as “A11yRCA” and add your feedback in the comment section.
Screenshots
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
Locate InputsWithRTL.json in the Adaptive Cards repository and inspect the edit-field definitions used by the UWP Visualizer. Add appropriate placeholder text for the Name, Edit, Phone, and Comments fields, then verify the card through the UWP Visualizer using the reported Tab-key navigation; done means each field exposes a meaningful placeholder.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- json
- Domain
- accessibility
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100