microsoft / microsoft/AdaptiveCards
[Adaptive Cards - Home Page] - Screen reader is not announcing the current page information for the 'Adaptive Cards' link control present on the header section on the page.
@SatwikKrSharma is already working on this.
Since Jan 12, 2026.
- 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)
Screen Reader: Narrator, NVDA
Repro Steps:
- Open the above URL on the Edge Dev browser.
- Navigate to the 'Adaptive Cards' link control present on the header section on the page using tab key.
- Press F12 to open the developer tool and inspect the code.
- Verify that, screen reader is announcing the current page information for the 'Adaptive Cards' link control present on the header section on the page or not.
Actual Result:
Screen reader is not announcing the current page information for the 'Adaptive Cards' link control present on the header section on the page.
Note
Same issue replicates with NVDA.
Expected Result:
Screen reader should properly announce the current page information for the 'Adaptive Cards' link control present on the header section on the page. This can be achieved by adding the aria-current="page" attribute to them.
User Experience:
Users who rely on assistive technologies will be impacted as the screen readers are not giving relevant information regarding the current page link present on the page.
WCAG Reference:
https://www.w3.org/WAI/WCAG22/Understanding/info-and-relationships.html
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/94f2b1ec-885e-462a-9cdf-26ea34daf710
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.
Assessment
This issue has not been assessed yet.