# Typography in UI

UI typography makes interface language readable, scannable, resizable, and structurally clear across devices, languages, states, and settings.

- Type: practice
- Domain: Experience & interface
- Level: Foundational
- Last reviewed: 2026-09-21
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/typography-in-ui/>)

## What it means

Typography in UI presents labels, instructions, data, and long-form text through typeface, size, weight, line height, spacing, measure, and hierarchy. It must support quick control recognition and sustained reading while remaining robust under zoom, text resizing, localization, and dynamic content.

## Why it matters

Text carries most interface meaning. Legible, consistent typography reduces errors, clarifies relationships, and supports scanning. A resilient type system also prevents clipped labels and broken layouts when users enlarge text or translations are longer than the source language.

## When to use it

Use a typography system from the first component, not as final styling. Define roles for headings, body, labels, data, and annotations, then test forms, tables, navigation, empty states, errors, and dense responsive layouts with real strings and user text sizes.

## How it works

1. Choose legible families with needed scripts, weights, numerals, and platform support.
2. Define semantic text roles and a restrained scale instead of styling screens independently.
3. Set readable line height and measure, allowing spacing to adapt without clipping.
4. Use weight, size, and position—not capitalization or color alone—for hierarchy.
5. Test zoom, font settings, translations, fallback fonts, loading, and high contrast.

## A practical example

A finance product defines roles for page titles, headings, body, labels, tabular numbers, and annotations. Amounts use aligned numerals, labels remain visible after entry, and containers grow at 200 percent text. Sensible fallbacks keep content readable during font download.

## Where it breaks

A type scale is not universal: distance, platform, language, and audience change readability. Thin weights and low contrast fail in real conditions. Web fonts add network cost, and truncation can hide meaning. Typography must be tested in context, not only as a specimen.

## Common mistakes

- Using placeholder text as the only field label
- Locking heights so enlarged or translated text clips
- Loading many font files without fallback or performance budgeting

## Sources

1. [Typography](<https://developer.apple.com/design/human-interface-guidelines/typography>) — Apple Human Interface Guidelines · Institutional guideline
2. [Understanding SC 1.4.12: Text Spacing](<https://www.w3.org/WAI/WCAG22/Understanding/text-spacing.html>) — W3C Web Accessibility Initiative · Accessibility guidance
3. [Typography](<https://designsystem.digital.gov/components/typography/>) — U.S. Web Design System · Government design system

## Related topics

- [Visual Hierarchy](<https://wiki.soroush.uk/topic/visual-hierarchy/>)
- [Color in UI](<https://wiki.soroush.uk/topic/color-in-ui/>)
- [Accessibility](<https://wiki.soroush.uk/topic/accessibility/>)
