- From: Roman Komarov via GitHub <sysbot+gh@w3.org>
- Date: Tue, 01 Apr 2025 19:15:41 +0000
- To: public-css-archive@w3.org
> Noting that WCAG is referenced by legislation ... so not just a naive case of "let's tweak WCAG then" Years pass, legislation changes. We're trying to design the language for the future. If the current specified criterion is absurd, it needs to be changed. Once it changes, and legislation catches up, the feature will stop violating it. Yes, those who are required by law to follow WCAG could not use the feature now, but could in N years from now on. > Also: a user wants to make text bigger. That's their prerogative. Coming along (as an author) saying "actually, I'd argue that no, that's not what you want" is ... maybe not the right approach. As someone who uses various methods of zooming text and content of pages every single day, I never want to “make text bigger”. I want to access content by increasing the size of small texts, usually paragraphs. This feature will not change anything in how minimum font-size works on pages, it will only allow authors to increase the size of certain elements to be conditionally _larger_ than they would be without it. At a smaller viewport, a header fully fitting into available space from the get-go, will be rendered at 20px size, and could be without issue increased in size to 40px via browser zoom. On larger viewports, the same header will be rendered at an already larger size. -- GitHub Notification of comment by kizu Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2528#issuecomment-2770452323 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 1 April 2025 19:15:42 UTC