{Linked:Bug6098050}[Sustainability Manager – Generate report using Copilot]: Keyboard focus indicator is not visible on “Take me there” link displayed after response is received

Is it an issue related to Adaptive Cards?

No.

What is the PWD impact?

Keyboard-only users may be unable to identify which element currently has focus while navigating through the Copilot response area. Users with low vision can lose track of their location on the page and may activate an unintended control. The absence of a visible focus indicator reduces navigation confidence and makes keyboard interaction significantly more difficult.

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?

Keyboard focus indicator

What is the public URL for the website?

No response

How to reproduce the issue?

1. Open the provided Dynamics 365 in Microsoft Edge and sign in using the supplied test credentials.
2. On the Record. Report. Reduce page, navigate to the Copilot button available in the header region and activate it.
3. Enter the prompt: "Create a water report in English for the period of January 2025 to January 2026 called 2025 water report" and submit it.
4. Wait until the Copilot response is generated and the "Take me there" link appears.
5. Using Shift + Tab, navigate to the "Take me there" link and observe the focus indication.

What do you expect?

The element should display a clearly visible keyboard focus indicator with a distinct four-sided focus boundary when it receives keyboard focus, consistent with other interactive elements on the page and sufficiently visible for keyboard-only and low-vision users.

What actually happened?

When keyboard focus moves to the "Take me there" link after the Copilot response is generated, the link receives keyboard focus programmatically; however, no visible focus indicator is displayed. Users cannot visually determine that the link currently has focus because the expected focus rectangle/boundary is absent.

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://liquid.microsoft.com/Web/Object/Read/ms.accessibility/Requirements/02.04.03

WCAG reference

https://www.w3.org/WAI/WCAG21/Understanding/focus-order

WAI-ARIA reference

No response

Adaptive Card JSON

Additional context

https://github.com/user-attachments/assets/d259299c-dd0d-4688-a40a-795f3bdfa04a

Reproduce the issue in Microsoft Edge with Narrator using the supplied Dynamics 365 steps, then inspect the rendered “Take me there” link and its focus styling in the Web Chat response area. Done means keyboard focus on the link shows a clearly visible four-sided indicator consistent with the other interactive elements.