microsoft / microsoft/BotFramework-WebChat

[White Label - Proactive]: At 320 view setting reflow mode, Proactive code is getting truncated.

Open
#5,699 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?

No.

What is the PWD impact?

At 320px view (reflow mode), the proactive code content is truncated, causing loss of information and preventing users—especially those who zoom content for accessibility—from fully viewing or completing required actions.

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 white label experience chat page and type Proactive word in type your message text box.
    4.Navigate to the search results.
    5.Verify that', at 320 setting, proactive code is getting truncated.
What do you expect?

At 320px view (reflow mode), the proactive code content should fully reflow and remain visible without truncation, ensuring no loss of information or functionality.

What actually happened?

At 320px view (reflow mode), the proactive code content is getting truncated.

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/reflow

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 through the webchat-loader URL using the listed 4.18.1-main version, mockBot, White Label experience, and the Proactive search result at 320px reflow. Inspect the rendered proactive code content in Edge with Windows Narrator; done means the full content remains visible without truncation at that viewport.

Written by the indexing model from the issue text.

Assessment

Domain
accessibility, frontend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.