- From: Adrian Roselli via GitHub <noreply@w3.org>
- Date: Tue, 09 Dec 2025 01:40:37 +0000
- To: public-css-archive@w3.org
>> 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. > > Isn't it exactly the same as the example from [the second note on the “understanding” SC 1.4.4 page](https://www.w3.org/WAI/WCAG22/Understanding/resize-text.html#:~:text=Note,-As)? No. See the final clause: "it should still be possible to get 200% text enlargement in some way compared to the default 100% zoom." It doesn't say to stop at 200%. You _satisfy_ the SC by getting to 200%, but you support _users_ by allowing larger. Otherwise the 500% setting is just a lie. Also, remember not all sites use media queries. Older sites do not and more and more modern sites ditch media queries in favor of more robust grid or flex layouts. Many sites that use media queries also don't resize the text at different breakpoints. Heck, I've argued for years to [not set text size](https://adrianroselli.com/2024/03/the-ultimate-ideal-bestest-base-font-size-that-everyone-is-keeping-a-secret-especially-chet.html). > The proposed limit is only for the text-grow algorithm in relation to the original size. When page zoom happens, it is fully analogous in behavior when the font-size is reduced for a narrower screen, and the “Understanding SC 1.4.4” says that this is enough to satisfy SC 1.4.4. See my point above that font size is not always reduced for a narrower screen. Assuming MQs are in use, or treating the solution as if MQs are ubiquitous, risks unexpected scaling. And again, 1.4.4 does not _cap_ text size at 200%. It sets 200% as the conformance target. -- GitHub Notification of comment by aardrian Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12886#issuecomment-3629815472 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 01:40:38 UTC