microsoft / microsoft/AdaptiveCards
[Adaptive Cards - "TextBlock" item from "Cards element"]: Incorrect heading structure is defined for the headings present under 'Text Block' screen.
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/explorer/TextBlock.html
OS Version: 23H2 (OS Build 26020.1000)
Browser Version: Version 122.0.2348.0 (Official build) dev (64-bit)
Tool: Accessibility Insight For Web
Repro Steps:
- Open the above URL on Edge Dev browser.
- Navigate to Headings and press enter key to turn on the toggle button 'On',
Actual Result:
While navigating to the 'Text Block' screen, incorrect heading structure is defined it is defined as 'H1 > H2 > H3 > H2'.
Expected Result:
Heading must be in logical order and Heading structure should be correct and its hierarchy should be as 'H1 > H2 > H3 > H4'. Inherited Properties heading should be defined as H2.
Note:
Same issue is repro under 'New Card' screen as 'Create, Explore and other headings' should be defined as H2 instead of H1,
User Impact:
Screen reader users will not get the context of the page if they navigate in heading mode as incorrect heading level announcement will be confusing for users as screen reader announces first Heading level 1 and then heading level 3.
WCAG Reference link:
[MAS 1.3.1 – Info and Relationships.docx (sharepoint.com)](https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships)
“ 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
Start with the Adaptive Cards Explorer TextBlock screen at https://adaptivecards.io/explorer/TextBlock.html and reproduce the heading tree using Accessibility Insight For Web. Compare the reported H1 > H2 > H3 > H2 structure with the expected H1 > H2 > H3 > H4 hierarchy, including the Inherited Properties heading and the New Card screen headings.
Written by the indexing model from the issue text.
Assessment
- Domain
- accessibility
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100