Format your text with search engines and accessibility in mind.
Think of headings as content guides — anyone should be able to understand the way you’ve organized your content by glancing at your headings. So make sure your headings are clear and descriptive.
Imagine the front page of a newspaper. In this context, an H1 is the big statement on the page (the purpose). H2s are smaller headings that fit into the big statement, and H3s are even more detailed.
To add a Heading:
Instead of configuring typography properties for each individual heading, you can use CSS to create Classes. Classes allow you to create a style for one heading and apply that style to other headings across your project.
To create a Class:
This Class will remember all the styling changes you make. If you change the font, or the weight, the Class (Big heading) will remember these changes. If you want to remove a change, you can reset that property.
To reuse a Class:
Now when you change a Heading — because you’re actually styling the Class — all Headings with that same Class will also change.
Tags let you change the default styling of text elements, like Headings, Paragraphs, and Links. Any stylistic changes you apply to a Tag or a Class will affect all related elements without having to update them individually.
To style a Tag:
Any style changes you make here will apply to every element with that Tag (e.g., All H1 Headings).
To learn more about how to pick your typography options, check out our blog post on web typography.
Text fills use clipping to apply color to the inside of text. A text fill uses the font color by default.
To add a custom text fill:
When you make a change to the gradient, it updates inside the text in realtime. You can put any background (or stack multiple backgrounds) using this method. When the background is clipped to text, it will ignore the font color and use the color in your Backgrounds section.
Parent elements can pass text style information down to their children. You can set text styles on parent elements to apply to their child elements and override these styles in the child element settings.
It’s common to use this technique to set global font styles on the body tag, to align text and other elements inside of sections, and to override default link block styles.
To use text inheritance:
The Body (All Pages) tag is the top-level tag. Changes to this tag (like the font) will pass down to all your text. This is a great way to set defaults on a project.
Maybe you want the paragraph font to be different from the default font. When you click into the font, you can see it taking cues from the Body (all pages) tag. When you change this font setting, it will apply a new class.
A class is automatically created on something the moment you style a specific property — this is the key to overriding default inheritance style. The orange indicator on the style property icon means there’s an inherited value for that property. Click the orange text to see where the value is being inherited from.
To override a default inheritance style:
Now you can click in to see the entire inheritance hierarchy.
See examples of how text style inheritance works.
Learn more about inheritance indicators in the Style panel introduction.
Spans is a formatting option to style specific parts of text elements, like individual characters or words.
To use span:
To clear span formatting:
Learn more about spans and inline text formatting.
Many typography units used on the web are set in pixels. But let’s look at some other options.
An em was originally based on the width of a typeface’s capital M. Ems look to their parent element and scale the font size proportionally.
So if a font is 16 pixels:
You can also set the font size on a paragraph’s parent element, like a Div block:
When the parent element is 20 pixels:
Rems are relative to the HTML font size.
A rem is calculated by taking your rem value and multiplying it by the HTML font size (which, unless you manually change it in the code, will respect the browser’s font size). This has the benefit of respecting a user’s browser preferences (if custom text size is set on the browser).
Like ems, percentage refers to the parent element's font size.
VW is a measurement of the width of the browser’s viewport that scales proportionally based on the width of the viewport.
CH is great for sizing something like a paragraph or a heading to limit the number of characters someone has to read per line.
For example, If a paragraph has a maximum width of 60ch, it takes the selected font (the paragraph’s typeface), and sets the paragraph’s boundary (its box) to equal the width of 60 zeros.
CH lets you set the WIDTH on a text element when you’re trying to limit the number of characters (again, based on the width of the font’s zero character.)
When it comes to font size, in most cases, pixel values are a safe bet. We have alternatives like ems, rems, percentages, viewport widths, and CH. The best way to get familiar with your options is to try them out inside a project and see how they interact. We can see these changes right on the canvas, and simulate browser and device widths at any time.
Accessibility and inclusive design are important to consider when designing for the web. Let’s look at some easy places to start making the web more accessible and inclusive when it comes to typography.
Thin fonts are extremely difficult to read — not only in Headings, but especially in paragraphs.
This is also the case with uneven weight distribution in a font — there are these kinds of characters that aren't very legible.
Make sure your font is no smaller than 16 pixels for body text.
Uneven vertical alignment on chunks of text (when text is centered, for example) can create a difficult reading experience. A jagged alignment makes it tough for the reader to follow from line to line.
Languages that distinguish between capitalized and lowercase letters are often far more legible when written in sentence case (e.g., “Sentence case”) or title case (e.g., “Title Case”). Essentially, you write out your text only using capitalization where it’s needed or expected.
All caps can introduce a heavier cognitive load for the reader, especially in longer paragraphs. Screen readers announce all caps as individual letters, interrupting the flow and making it difficult to understand. Consider limiting the use of all caps on longer strings of text.
There’s an expectation on the web that underlined text indicates a hyperlink. If you’re trying to draw emphasis, consider using italics or bold text (or make stylistic changes by wrapping things with a span).
Contrast is the measurement of the difference between background and foreground. Low contrast would be something like somewhat lighter gray on somewhat darker gray. Or maroon on red. Or purple on pink.
High contrast doesn’t mean we stop considering other things like font weight (a super thin font that happens to have high-contrast against the background is still super illegible.) But higher contrast usually leads to increased legibility, which is a great thing on the web.
You can use Webflow’s built-in Color contrast checker to assess the contrast ratio of your text against its background. And you can check the color contrast of your designs and learn more about best practices with these excellent color contrast tools, too:
Long lines of text confuse and tire a reader — their eyes have to travel really far from left to right. Use a container to constrict how far text spans horizontally across the page. 60 to 80 characters per line is recommended.
As we covered earlier, one way to do this is to set limits on the maximum width of a text element to however many characters you want in a line. Remember: (60 CH) is equal to 60 zeroes in whatever font you’ve selected.
Text with adequate line height makes it much less overwhelming and easier to track across and down a page.
Your line height should be at least 1.5 times the font size for paragraphs and blocks of text.
Your links should be meaningful and actionable. Screen readers can give visitors an overview of links on a page. When link text is read out of context, it should tell readers:
Listen to an example of a screen reader announcing unhelpful links on a page in the section about links from the video lesson above on Advanced web typography.
All your navigation should be tested, not just for what it’ll look like, but how you can interact with it using a screen reader. This is a great way to develop an understanding of how people can navigate your content.
We’re adding more and more teaching to Webflow University on the topic of accessibility and inclusive design, so keep checking back!
Something went wrong while submitting the form. Please contact firstname.lastname@example.org