2018-10-25
2364
#accessibility#html
Facundo Corradini
3883
Oct 25, 2018 ⋅ 8 min read

You’re using〈em〉wrong

Facundo Corradini Frontend developer, CSS specialist, best cebador de mates ever.

Recent posts:

Fix over-caching with dynamic IO caching in Next.js 15

Next.js 15 caching overhaul: Fix overcaching with Dynamic IO and the use cache directive.

David Omotayo
Aug 6, 2025 ⋅ 10 min read
LLMs are facing a QA crisis here’s how we could solve it

LLMs are facing a QA crisis: Here’s how we could solve it

LLM QA isn’t just a tooling gap — it’s a fundamental shift in how we think about software reliability.

Rosario De Chiara
Aug 4, 2025 ⋅ 7 min read

Windsurf vs. Cursor: When to choose the challenger

Windsurf AI brings agentic coding and terminal control right into your IDE. We compare it to Cursor, explore its features, and build a real frontend project.

Chizaram Ken
Jul 31, 2025 ⋅ 9 min read

The CSS if() function: Conditional styling will never be the same

The CSS Working Group has approved the if() function for development, a feature that promises to bring true conditional styling directly to our stylesheets.

Ikeh Akinyemi
Jul 30, 2025 ⋅ 12 min read
View all posts

2 Replies to "You’re using〈em〉wrong"

  1. As someone who’s just set out on learning HTML this week, this article really helped create that distinction between the two elements. It also highlighted that I might need to brush up on my use of the English language a bit. Most of it comes naturally to me as you said, but when you have to stop and think about how to markup your content, it really highlights the importance of knowing these rules. Thank you!

  2. I read this for a class assignment, and it was really enlightening (and entertaining!), but it also helped me with my language studies. Identifying the different scenarios where I’d use vocal stress in English helped me understand some mistakes I’ve been making in Turkish, which uses word order for many of those situations.

Leave a Reply