Post #2278184
2026-01-27 11:13 UTC
Replies (9)
-
@mahryekuh@hachyderm.io 2026-01-27 11:20
@joshtumath@mastodon.social I love this, thank you for proposing this idea! I hope to see it adopted in other browsers soon. Question: You mention one shouldn't mess with the base font size, and only use percentages if you do. However, do you see a difference in either of the following solutions with regard to the new meta tag? 1. `font-size: 100%;` 2. `font-size: 1rem;` 3. omitting `font-size` altogether on body.
-
@Kilian@mastodon.social 2026-01-27 11:21
@joshtumath@mastodon.social Looking forward to your presentation at CSS Day! Testing larger default font sizes is trivial in Polypane:
-
@Lukew@toot.wales 2026-01-27 11:28
@joshtumath@mastodon.social need to tweak my paddings a bit but even without that it works pretty well on my site!
-
@jscholes@dragonscave.space 2026-01-27 13:51
@joshtumath@mastodon.social @mahryekuh@hachyderm.io Apologies if I'm misreading it, but the "Why do I have to enable it" section was a bit unclear to me. Paraphrasing, it seemed to be saying: most websites violate WCAG by not accommodating text enlargement, and making text scaling the default would break those sites. But those sites are already broken for people who need a bigger text size. Either the user enlarges the text on desktop and breaks the layout, or enlarges it on Mobil and gets text that's too small to read. Would making text scaling the default not shine a light on how many websites are failing to meet accessibility requirements? Otherwise this meta tag is, in part, an optional accessibility support flag that sites can merrily continue to ignore.
-
@cwilcox808@c.im 2026-01-28 14:12
@joshtumath@mastodon.social > Even on smaller viewports, users should be able to increase the text size up to 200% without having to horizontally scroll. The relevant WCAG 2.2 guidelines are 1.4.4 Resize Text and 1.4.10 Reflow. Just to be clear, while it can be helpful and often achievable, WCAG doesn't require avoiding horizontal scroll with increased text size. Horizontal scroll needs to be avoided in viewports as narrow as 320px but only for the page as it was designed. Users also need to be able to enlarge text at least 200% but if they have to scroll in two directions to read it, so be it; enlarging by page zoom or even by pinch-to-zoom is sufficient to meet the Resize Text criterion. #a11y
-
@hdv@front-end.social 2026-02-02 09:05
@joshtumath@mastodon.social Woah, remember we talked about this at last year's @cssday@mastodon.social and it's already in a browser! Congrats on the progress, Josh!
-
@robinwhittleton@front-end.social 2026-02-02 09:58
@joshtumath@mastodon.social I’m sure I’m just missing something really obvious, but I’m having difficulty testing this. I’m on Chrome Canary 146 with experimental web platform features turned on, and I’ve added to my test page that has no font sizes applied to html (just ems, starting from body). I should just expect Mac’s General settings / Accessibility / Display / Text size slider to adjust the font size in the browser, right?
-
@timbrown@mastodon.social 2026-02-02 12:13
@joshtumath@mastodon.social 👏👏👏
-
@romainmenke@front-end.social 2026-02-02 19:37
@joshtumath@mastodon.social Awesome! Congrats on getting an idea into browsers 🚀 Added the meta tag to a couple of recent projects where I know it will work well. Getting an interface to work ok at 320px with a 32px preferred font size is really gratifying :)