microsoft / microsoft/BotFramework-WebChat

[Copilot - Send box: attaching a file]: Underline or chevron is not defined for links.

Open
#5,702 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A11yUsable Accessibility area-accessibility Bot Services BotFrameworkWebChat_Web bug customer-reported HCL-BIC
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?

When links are not visually distinguished with an underline or chevron, users may not recognize them as clickable, leading to missed navigation options, confusion, and reduced usability—especially for users with low vision or cognitive disabilities.

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?

Others or unrelated

What is the public URL for the website?

No response

How to reproduce the issue?
  1. Open URL: https://compulim.github.io/webchat-loader/ and sign in using valid credentials.
  2. Navigate to web chat page and select 4.18.1-main.20240927.ea7a875 (30/9/2024) version and then select mockBot link under present label and then select open web chat in new window link at bottom.
    3.Navigate to copilot experience chat page and attach an image file after selecting attachment icon and then send it.
  3. Observe that Underline/chevron is not defined for image link.
What do you expect?

Links should be clearly identifiable through visual indicators such as an underline, chevron, or other distinct styling to ensure users can easily recognize them as interactive elements.

What actually happened?

Underline or chevron is not defined for links.

Do you have any screenshots or recordings to repro the issue?
Image
Did you find any DOM elements that might have caused the issue?

No response

MAS reference

No response

WCAG reference

No response

WAI-ARIA reference

No response

Adaptive Card JSON

Additional context

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue from the webchat-loader URL using version 4.18.1-main.20240927.ea7a875, then inspect the rendered image link after sending an attachment. The work is done when the link has a clear visual indicator and the result is verified with Edge and Windows Narrator.

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
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.