microsoft / microsoft/AdaptiveCards
{Freeway-Bug}[Adaptive Cards- Blog tab]: The images on the cards get cropped at 200% zoom in blog page.
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 2k
- Forks
- 595
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 1
Description
Target Platforms
Other
SDK Version
1.6
Application Name
Adaptive Cards
Problem Description
Test environment:
OS: Win11
OS Version: 23H2 (OS Build 22631.5189)
URL: https://adaptivecards.io/
Edge dev Browser version: 137.0.3255.0 (Official build) dev (64-bit)
Screen reader: Narrator.
Pre requisites:
1.Set the display resolution as 1280*1024
2.Set the scale as 100%
3. Set the browser zoom to 200% and refresh the page.
Repro Steps:
1.Open URL in the Edge dev browser & sign in with valid credentials
2.Navigate and activate the blog tab and observe the issue
Actual Result:
The images on the cards get cropped at 200% zoom in blog page.
Expected Result:
The images on the cards should not get cropped at 200% zoom in blog page.
User Experience:
Low vision users relying on zoom will struggle to see page content if images on the cards are cropped at 200% zoom on the blog page.
MAS Reference:
MAS 1.4.4 – Resize Text
Screenshots
Card JSON
NA
Sample Code Language
No response
Sample Code
No response
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
Start at https://adaptivecards.io/, set the display resolution and browser zoom to the reported values, then open the Blog tab and compare the card images at 200% zoom. Done means the images are no longer cropped while the page remains usable for low-vision users; no source file or test is identified in the issue.
Written by the indexing model from the issue text.
Assessment
- Domain
- accessibility, frontend, web-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100