microsoft / microsoft/AdaptiveCards
{Linked:Bug3397076}[Adaptive Cards > New Card] - Visually appearing heading 'Explore' is not defined as heading.
Nobody has claimed this yet.
- 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/designer/
OS Version: 23H2 (OS Build 26040.1000)
Browser Version: Version 122.0.2365.3 (Official build) dev (64-bit)
Tool: Accessibility Insight For Web
Repro Steps:
- Open the above URL on Edge Dev URL.
- Press tab key and navigate to the 'New Card' and press enter key to activate it.
- New Card dialog will be appeared.
- Run the tool and observe the issue.
Actual Result:
Visually appearing heading 'Explore' is not defined as heading.
Expected Result:
Visually appearing heading 'Explore' must be defined as heading H1.
User Experience:
Users who rely on screen readers will not get the proper information of the UI properly when they navigate with quick heading navigation keys if visually appearing heading will not be defined.
WCAG Reference:
https://www.w3.org/WAI/WCAG21/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
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.
Research direction
The issue identifies https://adaptivecards.io/designer/ and the New Card dialog; start there and reproduce the problem with Accessibility Insights for Web, using heading navigation to inspect “Explore.” Done means “Explore” is exposed as an H1 and is reachable through heading navigation.
Written by the indexing model from the issue text.
Assessment
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100