microsoft / microsoft/BotFramework-WebChat
{Linked:Bug6098057}[Sustainability Manager - Generate report using Copilot]: “Take me there” link is not operable using Enter key after response is received
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 1.8k
- Forks
- 1.6k
- Avg merge
- 22h 58m
- Merged PRs (30d)
- 2
Description
Is it an issue related to Adaptive Cards?
No.
What is the PWD impact?
Keyboard-only users cannot activate the "Take me there" link and therefore may be prevented from accessing the generated report or related destination. Screen reader users may perceive the control as available but nonfunctional, resulting in task failure and loss of confidence in the interface.
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 navigation
What is the public URL for the website?
No response
How to reproduce the issue?
- Open the provided Dynamics 365 URL in Microsoft Edge and sign in using the supplied test account.
- On the Record. Report. Reduce page, navigate to the Copilot button available in the header region and activate it.
- 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.
- Wait for the response to be generated and navigate to the "Take me there" link using Shift + Tab.
- Press the Enter key on the focused link and observe the behavior.
What do you expect?
The element should be fully operable using the keyboard and activate its associated action when the Enter key is pressed while the link has focus.
What actually happened?
The "Take me there" link receives keyboard focus but does not perform its intended action when activated using the Enter key. The link appears interactive and is included in the keyboard navigation order; however, keyboard activation does not trigger navigation or execute the expected functionality.
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/keyboard
WAI-ARIA reference
No response
Adaptive Card JSON
Additional context
https://github.com/user-attachments/assets/15561af5-9996-4a83-8614-f1c6ca86a23c
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue in Microsoft Edge with Windows Narrator by generating the water report, then use Shift+Tab to focus the “Take me there” link and press Enter. Inspect the focused control and its activation behavior; done means Enter triggers the same navigation or action as the intended interaction. No source file or test is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- accessibility, frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100