Heading is not defined for ‘Adaptive Card design session’ text.

Is it an issue related to Adaptive Cards?

Yes, this is related to Adaptive Card. However, it does not repro on Adaptive Cards Designer.

What is the PWD impact?

When the “Adaptive Card design session” text is not defined as a heading, screen reader users and those relying on structured navigation cannot understand the hierarchy of the page. They may miss that “Breakfast” is a section title, making it harder to skim or jump directly to that content.

What browsers and screen readers do this issue affect?

No response

Are there any code-based customization done to Web Chat?

No, I am using Web Chat without any customizations except "styleOptions".

What version of Web Chat are you using?

Latest production

Which area does this issue affect?

Others or unrelated

What is the public URL for the website?

No response

How to reproduce the issue?

Repro Steps: ​

1. Open URL: Web Chat in edge browser.
2. Ask query 'Card Calendar'.
3. Navigate to message.
4. Observe the issue that Heading is not defined for ‘Adaptive Card design session’ text.

What do you expect?

Heading should be defined for ‘Adaptive Card design session’ text.

What actually happened?

Heading is not defined for ‘Adaptive Card design session’ text.

Do you have any screenshots or recordings to repro the issue?

https://github.com/user-attachments/assets/d18dc792-8d30-4ca0-851e-340cfc7675ad

Did you find any DOM elements that might have caused the issue?

No response

MAS reference

No response

WCAG reference

https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships

WAI-ARIA reference

No response

Adaptive Card JSON

Additional context

No response

Start with the Web Chat message produced by the “Card Calendar” query and inspect the rendered structure around “Adaptive Card design session” and “Breakfast.” Reproduce the screen-reader navigation issue in Edge, then verify that the affected text has appropriate heading semantics without disrupting the card hierarchy.