microsoft / microsoft/BotFramework-WebChat

Four-sided keyboard focus indicator is not visible on audio.

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

Nobody has claimed this yet.

A11ySev2 A11yWCAG 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?

Yes, this is related to Adaptive Card. However, it does not repro on Adaptive Cards Designer.

What is the PWD impact?

When the four‑sided keyboard focus indicator is not visible on audio controls, users who rely on keyboard navigation cannot determine which element currently has focus. This makes it difficult or impossible to operate audio playback, pause, or volume controls without a mouse.

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?

Repro Steps: ​

  1. Open URL: Web Chat in edge browser.
  2. Ask query 'Audio'.
  3. Navigate to Pay/pause control present in bot response.
  4. Observe the issue that Four-sided keyboard focus indicator is not visible on audio.
What do you expect?

Four-sided keyboard focus indicator should be visible on audio.

What actually happened?

Four-sided keyboard focus indicator is not visible on audio.

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

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

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 in Edge with Windows Narrator by asking Web Chat for “Audio” and navigating to the play/pause control. Inspect the control’s focus styling and compare it with the expected four-sided keyboard indicator; done means the indicator is visible while navigating audio controls.

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
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.