Post

I wish the @tailwindcss.com will revise some changes before releasing v4, especially concerning accessibility. It’s such a responsibility to get things right at their scale. Perhaps advanced features like breaking out of atomicity might be put behind a flag or at least discouraged by the docs? 🤔

Nmn@nmn.sh

Wrote my own thoughts on Tailwind 4. There’s a lot of good, some ok, and one terrible addition. I also added some thoughts about things that are longstanding issues in Tailwind that should be fixed. nmn.sh/blog/2024-11...

nmn.shThoughts on Tailwind 4Some thoughts on the latest Tailwind release

30/11/24, 2:14 pm0 reposts1 like

Kristóf Poduszló

@kripod.dev

30 Nov 2024

‘Reflow’ deserves more spotlight as a WCAG criterion. Visitors of a website should be able to browse content comfortably on a 320×256px viewport. That equals 400% zoom on a 1280×1024px screen but such an enlargement may also consist of 200% text-only + 200% UI zoom. www.w3.org/WAI/WCAG22/U...

w3.orgUnderstanding Success Criterion 1.4.10: Reflow | WAI | W3C

Kristóf Poduszló

@kripod.dev

30 Nov 2024

Also, @joshwcomeau.com wrote extensive guidance on the subtleties of px vs. rem www.joshwcomeau.com/css/surprisi...

joshwcomeau.comThe Surprising Truth About Pixels and Accessibility: should I use pixels or rems? • Josh W. Comeau“Should I use pixels or rems?”. In this comprehensive blog post, we'll answer this question once and for all. You'll learn about the accessibility implications, and how to determine the best unit to u...

Gusso

@gus.so

30 Nov 2024

oof, that was a good one