microsoft / microsoft/AdaptiveCards

[Adaptive Cards - Home Page] - Underline or chevron is not permanently defined for all the links present on the 'Adaptive Cards' home page.

Open
#9,300 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)
Tool: Developer Tool

Repro Steps:

  1. Open the above URL on the Edge Dev browser.
  2. Navigate to all the links present on the main section of the page using tab key.
  3. Press F12 to open the developer tool and inspect the code.
  4. Verify that, underline or chevron is permanently defined for all the links present on the 'Adaptive Cards' home page or not.

Actual Result:
Underline or chevron is not permanently defined for all the links present on the 'Adaptive Cards' home page.

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

Expected Result:
Underline or chevron should be permanently defined for all the links present on the 'Adaptive Cards' home page to identify it as link.

User Experience:
Cognitive limitation users are unable to differentiate between the normal static text and link text while the links present on the page are not highlighted with underline or chevron.

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.