microsoft / microsoft/AdaptiveCards

[Adaptive Cards - Schema Explorer] - Screen Reader is conveying the incorrect role as 'Link' for 'View' button.

Open
#8,359 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A11yMissing_HCLReviewed A11yRT A11ySev3 A11yWCAG 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.5

Application Name

Adaptive Cards

Problem Description

Test Environment:
OS: Version 22H2 (OS Build 25300.1000)
URL: https://adaptivecards.io/explorer/
Browser: Edge Dev Version 111.0.1661.36 (Official build) dev (64-bit)
Screen Reader: Narrator

Repro Steps:

  1. Turn on the Narrator using 'ctrl+win+enter' key.
  2. Open the above URL in edge dev browser.
  3. Navigate to the 'View' button under 'Publish Adaptive Card schema' and observe the issue.

Actual Result:
Incorrect role as 'Link' is defined for the 'View' button. It is announcing as 'View' Link.

Expected Result:
Correct role should be defined for the 'View' option and screen reader should convey the correct role information as 'View' button.

User Impact:
It will impact the screen reader user if the incorrect role as link is announced by the screen reader as user will not able to understand the actual functionality of the element.

MAS Reference:
https://www.w3.org/WAI/WCAG21/Understanding/name-role-value.html

“Have feedback to share on Bugs? Please help fill Trusted Tester Bug Feedback (office.com)

Screenshots

MAS4 1 2-Incorrect role as link is defined for the view button

https://user-images.githubusercontent.com/95913748/224330457-59cefc40-afe3-41d1-a9d4-9c45902eb794.mp4

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

Start at the Adaptive Cards Schema Explorer URL and reproduce the issue with Edge and Narrator by navigating to the View control under “Publish Adaptive Card schema.” Inspect how that control exposes its role, then verify that the completed change is announced as a button rather than a link.

Written by the indexing model from the issue text.

Assessment

Domain
accessibility, web-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.