[PWA Builder]: PWA Builder button text is getting overlaps with blog link after reflowing the page at 400 zoom.

[Anshi0420]

What happened?

When the page is reflowed at 400% zoom, the text associated with PWA Builder overlaps with the adjacent blog link.

How do we reproduce the behavior?

Pre-requisites :
Change the display resolution to 1280 * 1024 and zoom the browser up to 400% and enter full screen.

Repro Steps:

1. Open the given PWA Builder URL in Anaheim dev browser.
2. Observe the issue.

What do you expect to happen?

At 400% zoom, the text and elements on the page should remain properly spaced and readable without overlapping or obscuring each other.

What environment were you using?

OS Build: Windows 11 Enterprise Insider Preview 24H2 (26120.461)
Edge Browser: Version 123.0.2400.1 (Official build) dev (64-bit)
URL: https://www.pwabuilder.com/

Additional context

Observation:
This issue does not repro at 200 zoom.

User experience:
This issue makes it difficult for users viewing the page at 400% zoom to read the content, as the text overlaps with other elements. It affects readability and usability, particularly for users who rely on high zoom levels due to vision impairment or preference for larger text sizes. It may also cause frustration and confusion when navigating or interacting with the affected content on the page.

WCAG Reference:
https://www.w3.org/WAI/WCAG22/Understanding/reflow

Attachments:

[microsoft-github-policy-service]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .

[microsoft-github-policy-service]

This issue has been marked as "needs attention 👋" since it has not been triaged for 7 days. Please triage the issue .