microsoft / microsoft/AdaptiveCards

[Adaptive Cards- Expenses Report]: Screen reader is conveying incorrect role as Link for the 'Export as PDF' button.

Open
#9,024 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A11yCT A11yMissing_HCLReviewed 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: Dev (OS Build 27695.1000)
Browser Version: Version 130.0.2849.1 (Official build) dev (64-bit)
Screen Reader: Narrator

Pre-Requisite:
Turn on screen reader using caps + spacebar key.

Repro steps:

  1. Open the above URL in the edge dev browser.
  2. Navigate to the 'Sample' option and press enter key to activate it.
  3. Press tab key and navigate to the 'Expenses Report' link and press enter key to activate it.
  4. Press tab key and navigate to Export as PDF button and observe the issue.

Actual Result:
Screen Reader is conveying incorrect role information as Link for the 'Export as PDF' button. Currently role is defined as Link.

Expected Result:
Correct role should be defined as button so that when the focus lands on the 'Export as PDF' control then screen reader should announce the information as 'Export as PDF button.'

Note:
Same issue is repro with NVDA as well.

User Impact:
It will impact the screen reader user as they will get confused if the incorrect role as link will be defined for any control as on activating it user will assume that new tab or page will be open.

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/02eefd02-c0ef-408a-89e3-207409e47bff

Incorrect role as Link is defined for the Export as pdf

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.

Research direction

Open https://adaptivecards.io/ in Edge Dev and reproduce the Expenses Report flow with Narrator or NVDA, then inspect the implementation of the Export as PDF control. Confirm that the control is exposed as a button rather than a link, and repeat the keyboard and screen-reader steps to verify it is announced as “Export as PDF button.”

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
accessibility, frontend
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
48/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.