- From: Adrian Roselli via GitHub <noreply@w3.org>
- Date: Mon, 08 Dec 2025 21:48:58 +0000
- To: public-css-archive@w3.org
> 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). As noted, headings also need to scale to 200%. There is no exception for headings; they are the same importance as body text. Linking the [WCAG 2.2 1.4.4 Resize Text SC Understanding doc](https://www.w3.org/WAI/WCAG22/Understanding/resize-text.html) so folks are looking at the current one with normative language and the additional context it provides. Users have multiple non-AT methods to resize text with the last one being most common in my experience: * text size in the browser; * magnification; * browser zoom. Users who have to resize the page to 500% to get the text to 200% may not understand why 500% only gets them to 200% (and some may genuinely need 500%). This can result in bug reports and complaints (users will raise issues, because they already do and I have fielded them). I encourage you not to put an artificial cap on this at 200% and instead allow all browser-supported zoom levels. I recommend this issue also addresses [SC 1.4.12: Text Spacing](https://www.w3.org/WAI/WCAG22/Understanding/text-spacing.html), since authors sometimes use values relative to the text (such as unitless values for `line-height`) or hard-code values (like `px` for `line-height`). Not accounting for those can cause text overlap, violating 1.4.12. -- GitHub Notification of comment by aardrian Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12886#issuecomment-3629143152 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 8 December 2025 21:48:59 UTC