Keyboard Controls content marked as header but is not semantically a header.

[cryptasian]

Is it an issue related to Adaptive Cards?

No.

What is the PWD impact?

No response

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?

Keyboard navigation

What is the public URL for the website?

https://edfinancial.com

How to reproduce the issue?

This is feedback from the accessibility company Allyant who has been testing our website and has people who use screenreaders and other assistive technologies as a part of their testing team.

When content is marked up as a header, but is not semantically a header, it can be confusing for screen reader users.

What do you expect?

Remove the

tag.

What actually happened?

See other responses.

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

No response

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/WCAG22/Understanding/info-and-relationships

WAI-ARIA reference

No response

Adaptive Card JSON

No response

Additional context

No response