- From: Roman Komarov via GitHub <noreply@w3.org>
- Date: Fri, 05 Dec 2025 08:20:17 +0000
- To: public-css-archive@w3.org
> I think the default limit approach doesn't work well because a zoom-in operation will decrease the scaling factor in general. In the following example, changing 100% page zoom to 125% page zoom will decrease the scaling factor from 1.333 to 1.066, so the upper limit of the scaling factor won' affect. The important part is that browsers allow zooming up to 500%. That means that with 200% limit, a 400% increase will guarantee at least 200% increase in the font-size. For small zoom values there won't be a change, but that's ok and expected. The important part is the possibility to get the increased text _at all_ via available browser tools. > Firstly - the most important thing wrt. WCAG Resize Text is that the body/paragraph text gets bigger (e.g. the smallest text on the page). Its less important that heading text for example grows at the same rate (or grows at all). This was already argued in the original issue in a pretty long discussion, and there was a very strong pushback from a11y folks about this. For anything related to WCAG, it doesn't matter if the specific SC lacks nuance, if the heading text will not grow, it could lead to a violation. This responsive text pattern is also criticized in the same way. -- GitHub Notification of comment by kizu Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12886#issuecomment-3615767207 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 5 December 2025 08:20:18 UTC