microsoft / microsoft/AdaptiveCards

[Adaptive Cards - Blog] - There is no 'H1' heading defined for the blogs page.

Open
#8,551 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A11yMissing_HCLReviewed A11yPwD-AT A11yRT A11yUsable AdaptiveCards_Web Area-Accessibility Area-Renderers Bug GradeB 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 23H2 (OS Build 25381.1)
URL: https://adaptivecards.io/blog/
Browser: Edge Dev Version 115.0.1901.5 (Official build) dev (64-bit)
Tool: Accessibility Insight For Web

Repro Steps:

  1. Open the above URL in the edge dev browser.
  2. Run the tool and observe the issue.

Actual Result:
There is no H1 heading programmatically and visually defined on the blog page. Only H2 and H3 headings are defined.

Expected Result:
There should be programmatically and visually 'H1' heading should be defined on the blog screen.

User Impact:
It will impact the low vision user if there is no H1 heading is visually defined.

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

Screenshots

Usable - There is no H1 heading is defined for the Blog screen

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 by inspecting the blog page at https://adaptivecards.io/blog/ and identify the source that generates its page heading structure. Verify the current heading hierarchy with an accessibility tool, then ensure the blog page has one visually and programmatically defined H1 heading and rerun the accessibility check.

Written by the indexing model from the issue text.

Assessment

Domain
accessibility, web-dev
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.