microsoft / microsoft/AdaptiveCards

[Adaptive Cards - Home Page] - 'Visit the hub' control present on the main section of the page visually appears as normal static texts in 'Aquatic and Desert' modes.

Open
#9,301 0 comments 0 reactions 1 assignee View on GitHub

@SatwikKrSharma is already working on this.

Since Jan 12, 2026.

A11yMissing_HCLReviewed A11yRT A11yUsable AdaptiveCards_Web Area-Accessibility Area-Renderers Bug HCL-AdaptiveCards-Web HCL-E+D MissingReviewedDeprecated Product-AC
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: 25H2 (OS Build 26200.5761)
Browser Version: Version 145.0.3734.1 (Official build) dev (64-bit)

Pre-requisites:
Turn on 'Aquatic/Desert' theme' (Navigation Path: System Settings> Accessibility > Contrast theme>Aquatic/Desert theme)

Repro Steps:

  1. Open the above URL on the Edge Dev browser.
  2. Navigate to the 'Visit the hub' control present on the main section of the page using tab key.
  3. Verify that, 'Visit the hub' control present on the main section of the page visually appears as normal static texts in 'Aquatic and Desert' modes or not.

Actual Result:
'Visit the hub' control present on the main section of the page visually appears as normal static texts in 'Aquatic and Desert' modes.

Note:
Same issue replicates for the 'Visit the hub' links present on the 'Schema Explorer', 'Samples' and 'Blog' page

Expected Result:
'Visit the hub' control present on the main section of the page should be properly appear as interactive 'hyperlink' control as per the format of in 'Aquatic and Desert' modes. They must not display as static text in any theme.

User Experience:
People with visual disabilities who rely on high contrast themes to see content properly will be impacted if the 'Visit the hub' control appear as plain text in 'Aquatic' and 'Desert' modes. Without clear visual identification or interactive elements, users may be unable to identify the control. This limits their ability to navigate or refine data on the page. As a result, accessibility and usability are significantly reduced for affected users.

Have feedback to share on Bugs ? please tag bug as “A11yRCA” and add your feedback in the comment section

Screenshots

Image

Card JSON
NA
Sample Code Language

No response

Sample Code

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.