{Linked:Bug(6098029)}[Sustainability Manager - Generate report using Copilot]: Screen reader announces irrelevant information instead of generated response results when asking questions.

[Rinkoo90]

Is it an issue related to Adaptive Cards?

No.

What is the PWD impact?

Screen reader users experience unnecessary delays before hearing the Copilot response. Excessive and irrelevant announcements increase cognitive load and frustration. Users may miss or lose context of the actual response due to verbose or incorrect reading order.

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?

Live region

What is the public URL for the website?

No response

How to reproduce the issue?

1. Open URL: https://msms2prod.crm8.dynamics.com/main.aspx?appid=e43db999-bd0d-f111-8407-0022486e5c5a&pagetype=control&controlName=msdyn_MscrmControls.SUS.HomePageControl and login with given credentials (sustainability@capintegration01.onmicrosoft.com)
2. Record. Report. Reduce page opens. Navigate to Copilot present on header region & select it
3. Give the following prompt to generate water report, "Create a water report in English for the period of January 2025 to January 2026 called 2025 water report"
4. Navigate to the tools icon and activate it. Bing Search popup will appear and try to enable/disable switch button.
5. Observe the issue.

What do you expect?

When the generated response is available, the screen reader should announce only the relevant response content (or a concise status message such as “Response received”), without announcing unrelated or previously rendered information.

What actually happened?

When a user asks a question and the generated response (received results) is displayed, the screen reader announces extra, irrelevant information before reading the actual Copilot response. As a result, screen reader users must listen to unrelated content before reaching the intended answer.

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/MAS4.1.3

WCAG reference

https://www.w3.org/WAI/WCAG21/Understanding/status-messages.html

WAI-ARIA reference

No response

Adaptive Card JSON

Additional context

No response