- From: Adrian Roselli via GitHub <noreply@w3.org>
- Date: Tue, 09 Dec 2025 00:15:12 +0000
- To: public-css-archive@w3.org
> How do you suggest the SC 1.4.4 could be achieved for the case of browser zoom reducing the effective viewport size if we won't introduce a default cap to 200%? I don't understand how _introducing_ a text scale limit of 200% meets 1.4.4. You need to _meet_ 200%, but that doesn't mean you stop at 200%. Let users zoom as much as the browser allows. > Do you consider https://github.com/w3c/csswg-drafts/issues/12886#issuecomment-3556253205 to detect the browser zoom at initial page load and then scale text while considering the difference between the size on load and the following zoom factor worth the potential font-size change after a refresh? Not at first glance, no. A user may scale the page up and down repeatedly without navigating to get the size they can read and may need different scale factors on different pages (home page versus a product page versus a press release). Which means when they come back to any page and they get a "different rendering outcome," they may assume something has broken, disappeared, or otherwise changed. It also adds a not-insignificant burden to people who test WCAG (human and tools) as it suggests they need to test a page first by resizing on the page and then by reloading the resized page. That would impact 1.4.4, 1.4.10, 1.4.12, and potentially 2.4.11 & 2.5.8. I should note that I am also not a browser engineer, so I may be misunderstanding the terminology used. -- GitHub Notification of comment by aardrian Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12886#issuecomment-3629601500 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 9 December 2025 00:15:13 UTC