[Supporting Platform - Bot Framework Web Chat - Card Breakfast]: In 320*256 pixel mode 'White-labelled', 'Copilot' and 'Fluent UI' controls are not visible. #5364
Labels
area-accessibility
Bot Services
Required for internal Azure reporting. Do not delete. Do not change color.
bug
Indicates an unexpected problem or an unintended behavior.
customer-reported
Required for internal Azure reporting. Do not delete.
Is it an issue related to Adaptive Cards?
No.
What is the PWD impact?
User Experience:
When users with low vision resize the page to the viewport of 320*256 pixel, it will be difficult for them to understand the content if the contents or controls on the page appear overlapped or truncated as they are the source of visual information on the page.
Pre-requisite:
Achieve viewport 320 X 256 by adjusting the browser. (Open the developer's tool, resize, and zoom the browser to achieve viewport 320 X 256).
Note:
User credentials should not be included in the bug.
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?
https://compulim.github.io/webchat-loader
How to reproduce the issue?
What do you expect?
In 320*256 pixel mode 'White-labelled', 'Copilot' and 'Fluent UI' controls should be visible clearly.
What actually happened?
In 320*256 pixel mode 'White-labelled', 'Copilot' and 'Fluent UI' controls are not visible.
Observation: In normal mode the controls are clearly visible.
Do you have any screenshots or recordings to repro the issue?
https://github.com/user-attachments/assets/67138d6c-5467-491e-9bdf-b0c7120cf619
Did you find any DOM elements that might have caused the issue?
No response
MAS reference
MAS 1.4.10 – Reflow
WCAG reference
No response
WAI-ARIA reference
No response
Adaptive Card JSON
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: