Heading is not defined for ‘Breakfast’ 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 “Breakfast” 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?

Windows: Edge with Windows Narrator

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 Breakfast'.
3. Navigate to message.
4. Observe the issue that Heading is not defined for ‘Breakfast’ text.

What do you expect?

Heading should be defined for ‘Breakfast’ text.

What actually happened?

Heading is not defined for ‘Breakfast’ text.

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

https://github.com/user-attachments/assets/5a7beb2e-2063-4533-9fba-720a455327bd

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 by reproducing the issue in Edge with Windows Narrator using the reported “Card Breakfast” query, then inspect the rendered message and its accessibility structure. Done means “Breakfast” is exposed as a heading and structured navigation identifies it as a section title.