microsoft / microsoft/AdaptiveCards

[Adaptive Cards - "TextBlock" item from "Cards element"]: Incorrect heading structure is defined for the headings present under 'Text Block' screen.

Open
#8,798 0 comments 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
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:

  1. Open the above URL on Edge Dev browser.
  2. 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

Incorrect heading order is defined

Incorrect heading level is defined

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 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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.