DEV Community

BM lm
BM lm

Posted on

Typography QA: catching wrong-font bugs before they ship

A wrong font in production is a sneaky bug: no console error, no failed test - just a page that looks 5% off and a brand manager who notices immediately.

Why it happens

  • A font-family fallback silently swaps to Helvetica when the licensed webfont 404s.
  • A redesign ships with the old brand font still cached in the CDN config.
  • A vendor delivers assets in a lookalike free font because nobody checked the license paperwork.

The pre-ship check that catches it

Screenshot the key headline at production size and verify it against the spec - not by memory. If the spec itself is in doubt (legacy sites, rebuilt brand kits), identify the actual typeface first. On-device tools like Typeye do this from a screenshot without uploading client material anywhere.

Make it a pipeline step

  • Keep the canonical font names in a single config file, not scattered across components.
  • Add a visual regression snapshot on the typography-heavy pages.
  • When a snapshot diff fires, identify the rendered font from the snapshot itself - it takes seconds and removes the guesswork.

Typography bugs are cheap to catch and expensive to explain. One screenshot per release, checked properly, is the whole discipline.

Top comments (0)