microsoft / microsoft/AdaptiveCards
[AdaptiveCards- Schema Explorer]: In high contrast mode, Feedback link appears as a button.
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.5
Application Name
Adaptive Cards
Problem Description
Test Environment:
URL: https://adaptivecards.io/explorer/
OS Version: 22H2(OS Build 25300.1000)
Browser Version: Version 11!.0.1661.27 (Official build) dev (64-bit)
Pre-requisites:
Settings > Accessibility > Contrast themes >High-contrast Aquatic and Dessert modes.
Repro Steps:
- Open the above URL in edge dev browser.
- Navigate to the 'Feedback' link and observe the issue.
Actual Result:
'Feedback' link is defined as a 'Link' but in high contrast mode it appears as a button.
Expected Result:
In high contrast mode, 'Feedback' link should appear as a link.
User Experience:
When ‘Feedback’ link is appearing as button in high contrast modes, users who rely on that feature are blocked from information and functionality of the full user experience within the site/app.
"Have feedback to share on Bugs ? Please help fill Trusted Tester Bug Feedback (office.com) “.
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
Open https://adaptivecards.io/explorer/ in Edge Dev and enable the Aquatic and Desert high-contrast themes to reproduce the Feedback control appearance. Trace the Schema Explorer entry point responsible for that control; done means Feedback retains link semantics and appears as a link in both high-contrast modes.
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
- Needs clarification
- Newbie friendliness
- 25/100