Post #2809171

2026-01-27 15:45 UTC

@joshtumath@mastodon.social @jscholes@dragonscave.space @mahryekuh@hachyderm.io for something like color scheme if we had made that honour dark mode all of a sudden it would have caused a lot of breakage and led to very real accessibility issues (contrast bugs galore). Whereas in this case it does seem to be opt-in already (by virtue of having changed that font-size setting)?

Replies (1)

@jscholes@dragonscave.space 2026-01-27 15:58

@Lukew@toot.wales Yes, this is a good articulation of what I was getting at. Thanks. The complete lack of text scaling on mobile platforms seems a fundamental failing on the part of browser vendors. Perhaps framing this as an optional feature for web authors makes it more likely that those same browser vendors will be willing to do something about it, even though it's a situation they have created. Likewise, I can see the logic in website owners having a way to avoid their layouts becoming fundamentally unusable when large text is applied, until they've done the work to support it and flipped the switch. A non-functional site is probably unpalatable to most stakeholders, many of whom would unfortunately not decide to solve that problem by fixing their own output. But both of these issues get to the heart of my discomfort. Namely that making this an opt-in feature seems more in service of historically bad actors than good ones. "Resize text" was first added to WCAG in May 2007. @joshtumath@mastodon.social @mahryekuh@hachyderm.io

Open ##2809172