Variable fonts can generate a wide range of styles from a single file, but the default browser styling of <b> and <strong> does not keep up with the full span of font-weight values these fonts expose.

How each engine handles the default weight

Both elements exist to draw attention to a word or passage, and user agent stylesheets accomplish this by raising font-weight. The trouble starts when the surrounding text already carries a custom weight. Base text sits at 400, yet font-weight accepts any number from 1 to 1000 inclusive.

Chrome applies a constant 700 to <b> regardless of context, and Safari does the same. Firefox instead picks between 400, 700 and 900 based on the weight of the parent text. The gap stems entirely from divergent user agent stylesheets for these elements.

/* Chrome and Safari’s user agent stylesheet */
strong, b {
  font-weight: bold;
}

/* Firefox’s user agent stylesheet */
strong, b {
  font-weight: bolder;
}

The CSS Fonts module defines both bold (equal to 700) and bolder, a relative weight. When bolder is used, the resolved value falls back to one of the three values Firefox uses:

If the outer text has a font-weight of…the bolder keyword computes to…
1 to 349400
350 to 549700
550 to 899900
900 to 1000No change (same value as outer text)

Which engine matches the specification

font-weight itself belongs to the CSS Fonts module, but the recommended weights for individual HTML elements live in the Rendering section of the HTML Standard. That standard has suggested bolder instead of bold since 2012.

/* The HTML Standard suggests the following user agent style */
strong, b {
  font-weight: bolder;
}

Firefox is currently the only engine following the recommendation. Because Chrome and Safari never switched, the widely used Normalize stylesheet ships a rule that forces bolder consistently across browsers.

Each default fails somewhere

Matching the standard does not automatically make Firefox's behavior superior. Both approaches break down, just at opposite ends of the scale. Chrome's constant bold stops producing visible contrast near 700 and above, while Firefox's relative approach fails around 300.

Firefox's worst case is severe: bold text can become nearly invisible. At a parent weight of 349, Firefox resolves <b> to 400 — a shift of only 51 points, which the eye can barely register.

Three paragraphs of text about English scientist Tim Berners-Lee. All of the text appears to be the same font weight.
(View on CodePen)

What to do about it and where the spec may go

Pages that use thin weights or variable fonts below 350 should account for this. Explicitly setting font-weight for <b> and <strong> is safer than trusting the browser default, which raises the weight by an insufficient amount.

/* Defining the regular and bold font-weight at the same time */

body {
  font-weight: 340;
}

b,
strong {
  font-weight: 620;
}

Beyond patching individual sites, bolder is regarded as outdated and poorly suited to variable fonts. The desirable behavior is emphasis that reads clearly no matter what weight the surrounding text uses, which would require the browser to add roughly the same increment in every case.

The CSS Working Group has discussed permitting percentages in font-weight, mirroring how font-size works. As Lea Verou put it:

A far more common use case is when we want a bolder or lighter stroke than the surrounding text, in a way that’s agnostic to the weight of the surrounding text.

/* Increasing font-size by 100% */
h1 {
  font-size: 200%;
}

/* PROPOSAL - Increasing font-weight by 50% */
strong, b {
  font-weight: 150%;
}

With variable fonts in mind, a value such as 150% would likely serve as a better default than the bold/bolder pair browsers rely on now.