{Linked:Bug39039304 }[Agent Builder Skills][Preview Tab][Screen Reader]: Section headings for Justification, User impact, Business impact, and Scope are not exposed as heading levels

[Kjasnani7]

Is it an issue related to Adaptive Cards?

No.

What is the PWD impact?

Screen reader users rely on heading navigation to quickly understand page structure and move between sections. When these section titles are not exposed as headings, users must read through content sequentially to locate important information, making navigation slower and less efficient.

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?

ARIA roles

What is the public URL for the website?

https://aka.ms/agentbuilder-native-msit

How to reproduce the issue?

1. Open the Agent Builder Skills application using the provided URL and sign in with valid credentials.
2. Navigate to "Agents and Skills" and activate it.
3. Create an agent with a valid skill and complete the setup flow.
4. Navigate to the "Preview" tab and activate it.
5. Enter a prompt that invokes the added skill and submit it.
6. Inspect the generated response content using Accessibility Insights, browser developer tools, or screen reader heading navigation commands.
7. Observe the sections Justification, User impact, Business impact, and Scope.

What do you expect?

The element should expose Justification, User impact, Business impact, and Scope as programmatically determinable headings using appropriate semantic heading markup or equivalent ARIA heading roles with valid heading levels so that assistive technologies can accurately convey the document structure.

What actually happened?

The sections Justification, User impact, Business impact, and Scope are visually presented as section headers; however, they are not programmatically exposed as heading elements. As a result, assistive technologies do not identify these section titles as headings, and users cannot navigate directly to them using heading navigation commands.

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

https://aka.ms/MAS1.3.1

WCAG reference

No response

WAI-ARIA reference

No response

Adaptive Card JSON

Additional context

39039304_.Agent.Builder.Skills.Web.Testing.an.agent.with.a.skill.in.the.Preview.tab.ScreenReader.webm