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

What do you expect?

Heading should be defined for ‘Alaska Airline’ text.

What actually happened?

Heading is not defined for ‘Alaska Airline’ text.

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

https://github.com/user-attachments/assets/a3bd8365-81f5-428b-9ed6-93554014c40d

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 Web Chat message in Edge with Windows Narrator and inspect the rendered Adaptive Card structure for the “Alaska Airline” and “Breakfast” text. No source file or test is identified in the issue; done means the text is exposed as the intended heading and screen-reader users can understand the section hierarchy.