Font weight controls how thick or bold text appears. Thin text can be harder to read, especially at small sizes, so weight matters alongside font size, typeface, and contrast. section 3.1.1 section 4.3
For body text, use a weight of 400 or higher; increase it when the typeface has thin strokes. Headings and interface controls can use heavier weights for clarity. section 4.3
Table 4.1 Choosing fonts for better readability in web applications
|
Attribute
|
Recommendations
|
|
|
Size and weight
|
Body text
|
Font size of at least
1rem (this defaults to 16px in most browsers, depending on their default root element font-size – and it is strongly recommended not to override it).
Font weight of 400 (or more if the font is thinner).
|
|
Headings
|
More flexibility in style.
Font size should be larger than body text. It also varies depending on the heading level (ideally, from
1.125rem
(
18px
) for
<h6>
to
2rem
for
<h1>
).
<h5>
and
<h6>
can have the same size and be distinguished using some styling, such as italicized text.
Larger weight than body text (for example 500 or more).
|
|
|
Text in UI controls
|
Font size should be equal to or greater than the body text.
Use medium or bold weights for more clarity.
|
|
|
Typeface
|
Serif vs sans-serif
|
Serif fonts, such as Times New Roman, have ornamental strokes (feet) that may reduce legibility at smaller sizes or lower resolutions. Sans-serif fonts, such as Arial, are cleaner and are often used for web interfaces.
In reality, however, the choice between serif and sans-serif fonts does not matter as much as how the text is presented in terms of size, spacing, weight, contrast, and font clarity. These factors significantly impact readability. Generally speaking, sans-serif fonts are considered a safer choice for web interfaces, particularly for body text and UI controls. This is because they maintain readability at lower resolutions – if used well.
When opting for sans-serif fonts, consider those with a tall x-height. This refers to the distance between the baseline and the top of a lowercase letter “x”, in any given typeface, as shown in the following image. Fonts with a tall x-height make lowercase letters without ascenders or descenders, such as a, e, s, c, and o, larger relative to the font size and more legible.
|
|
Font family
|
Avoid decorative or overly stylized fonts, especially for body text, form fields, navigation, and UI controls. Choose readable, well-tested fonts with highly distinguishable characters. When a project does not require custom or brand-specific fonts, system UI fonts may be a practical choice, as they are typically designed for on-screen readability and are familiar to users. In CSS,
system-ui
(along with
-apple-system
for older Apple browsers) in the
font-family
property tells the browser to use the operating system’s default UI font, such as Segoe UI on Windows, San Francisco on macOS, and the desktop environment's default font on Linux (for example, Adwaita Sans in GNOME from version 48 onwards).
Fonts that perform well from an accessibility perspective include Inter, Noto Sans, and Source Sans Pro, while widely available system fonts like Arial and Verdana are also good choices.
|
|
|
Generic fallback
|
A generic fallback is required. Adding
sans-serif to the end of the
font family ensures the browser will always pick up any available sans-serif font from the user’s device.
|
|
|
Color and contrast
|
Content and UI controls
|
Use darker text and heavier weights for better contrast.
Always test text contrast using a contrast checker.
Avoid light-colored text with thin-stroked typefaces.
See section 3.1 for an in-depth discussion.
|
Compare recommended font weights for body text, headings, and interface controls. section 4.3
A thin body-text style
A body style using font-weight: 300 can make small, thin-stroked text harder to read. Increase the weight and check the text size and contrast, especially if keeping a decorative typeface. section 4.3



