Stacking <strong> and <em> on the same words was once a manual chore in pre-WYSIWYG days, and it raises a fair question: does doubling up on emphasis tags actually accomplish anything? The two elements carry different meanings, so they are not interchangeable, and nesting one inside the other adds no benefit.

Two Tags, Two Jobs

<strong> and <em> have been distinct since HTML5:

  • <strong> conveys "strong importance, seriousness, or urgency for its contents."
  • <em> represents "stress emphasis."

Think of <strong> as adding weight to a warning: Warning: The following content has been flagged for being awesome. The italics that <em> produces can grab the eye, which makes it tempting for the same purpose, but its actual job is to hint at where a reader should place stress. Two versions of one sentence can put the stress on different words; read aloud, they sound different, and the sentence means something different. <strong> does not shift meaning that way. That makes <em> a tool for tone.

Italics and Bold Without Semantic Weight

Sometimes content needs to look italic or bold without any change in meaning. Several other tags render italics and carry their own semantics:

  • <i> was the classic emphasis tag before HTML5, applied with italics everywhere. Today it italicizes visually and changes nothing semantically.
  • <cite> marks the source of a fact or figure, as in "Source: CSS-Tricks."
  • <address> marks contact information — email addresses and phone numbers, not just physical addresses.

<strong> follows the same logic: for text that should simply look boldfaced, <b> avoids attaching importance that isn't there. Remember that browsers already render headings in bold by default, so no extra strong emphasis is required.

When Emphasis Meets Content That Is Already Styled

Legitimate cases exist for italicizing part of an emphasized line, or emphasizing part of an italicized one. Blockquotes are a common example — they are frequently italicized for style even though default browser styles leave them upright. If a movie title inside such a blockquote needs italics with no stress emphasis, <i> is the right choice, but italic text inside italic text looks wrong. The rule is to remove the italics from the nested element:

blockquote i {
  font-style: normal;
}

Container style queries handle these cases well once available. The snippet checks whether the blockquote's font-style is italic and, if so, renders <em>, <i>, <cite> and <address> as normal text while keeping whatever semantic meaning each one has.

blockquote {
  container-name: quote;
  font-style: italic;
}

@container quote (font-style: italic) {
  em, i, cite, address {
    font-style: normal;
  }
}

Why Not Nest One Emphasis in Another

Neither <strong> inside <em> nor <em> inside <strong> is worth writing:

<p>I ate the <em><strong>entire</strong></em> plate of burritos.</p>
<p>I ate the <em><strong>entire</strong></em> plate of burritos.</p>

Rendering itself is fine, and in modern browsers the order doesn't matter — Jennifer Kyrnin notes that some browsers render only the tag nearest the text, though limited testing didn't turn up such a case. The real reason to avoid it is that it isn't needed. No grammar rule calls for it; as with exclamation points, one form of emphasis suffices, chosen to match the goal — visual, weight, or announced emphasis. Nor does nesting add an accessibility perk: some screen readers announce emphasized content, but they don't read the markup with any extra importance or emphasis.

If the Emphasis Really Must Be Maximal

When the demand is for all the emphasis, reach for the right tag for the type, then add styles with semantically neutral tags and CSS to cover what browser defaults miss:

<style>
  /* If `em` contains `b` or `u` tags */
  em:has(b, u) {
    color: #f8a100;
  }
</style>

<p>
  I used to have this boss who <em>loved</em>, <strong>loved</strong>, 
  <strong><em>loved</em></strong>, <strong><em><u>loved</u></em></strong> 
  to emphasize words.
</p>

Applying the same defensive approach to <strong> is reasonable:

/* If `em` contains `b` or `u` tags */
em:has(b, u),
/* If `strong` contains `em` or `u` tags */
strong:has(i, u) {
  color: #f8a100;
}

Error detection helps too — nested emphases can be highlighted in red so problems are visible:

/* Highlight semantic emphases within semantic emphases */
em:has(strong),
strong:has(em) {
  background: hsl(0deg 50% 50% / .25);
  border: 1px dashed hsl(0deg 50% 50% / .25);
}

Then combine it with the snippet that strips default italics from an element nested inside an italicized one.

Practical Safeguards

  • Confirm the webfont ships bold and italic variations; otherwise the browser will fake bold or italics itself. Keep font files limited to the weights and styles actually used for better performance.
  • If the formatting seems off, consider rewriting the content — phrasing can supply emphasis naturally.
  • Check analytics for the browsers visitors use and test against them. No tested browser objected to <strong> within <em> or the reverse, but other browsers might.