- From: davidsgrogan via GitHub <noreply@w3.org>
- Date: Wed, 15 Apr 2026 20:47:30 +0000
- To: public-css-archive@w3.org
> <TabAtkins> dgrogan: right now in Chrome in the a11y UI, we allow the user to change the default font size, "medium", to a max of 72px, 600% My math didn't math. 72/16 = 4.5, not 6. So, we let users change `medium` to a max of 450%, not 600%. The qualitative points still stand though, namely: > I'm not sure why this would be a regression from earlier (Just recapping what I said on the call) There are Chrome desktop users _today_ that have changed their `medium` font size from `16px` to `64px` because `64px` makes web text readable for them. (Other users obviously browse at `24px`, `32px`, `48px`, etc). When these users browse the web, many layouts are broken or at least render differently than what the author expects. But these users empirically, _not hypothetically_, still derive value from browsing the web at their larger sizes. If we implement this proposal, and a site adds `<meta name="text-scale" content="32px">`, then our `48px`, `56px` and higher..., users can **no longer read** that site. That's the regression. -- GitHub Notification of comment by davidsgrogan Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13557#issuecomment-4255352249 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 15 April 2026 20:47:31 UTC