Props
Usage guidelines
- Any time that text is needed in the UI as a label, paragraph or number display
- When you need to use a semantic H1–H6 heading to create a clear typographic hierarchy and page structure. Use Heading instead.
Best practices
Emphasize text inside of paragraphs by using a bold weight.
Use size to emphasize things like numbers that don’t define a page structure.
Use a minimal amount of sizes and styles to keep the UI clean and readable.
Mix styles and alignment, as this can be hard to read and follow.
Start-align paragraph text.
Center-align paragraph text. This is hard to read, especially for users with dyslexia.
Accessibility
Accessible sizing
A minimum text size of 16 px (12pt) is recommended for readability. Some short text labels, or secondary text can go lower than that, but smaller sizes should be kept to a minimum. Making text brief will also help with readability.
Accessible color
For low-vision users, text color contrast is very important. To insure accessible contrast, stick to our standard text colors. See our accessibility page for design considerations and handy accessibility tools for checking color contrast.
Localization
Keep text simple and short to avoid truncation or line wrapping in UI controls like buttons when translating languages that require more characters. Avoid overriding our line-height settings, as this can result in text clipping for scripts, like Hindi, that have taller ascenders and descenders.
Text-wrapping and hyphenation
Hyphenation on iOS is turned off by default to avoid incorrect word breaks when strings of text wrap to the next line. This is especially helpful for international languages where an incorrect word break can greatly change the meaning of a word or sentence.
Variants
Alignment
Use align
to adjust the positioning of text within wrapper elements.
Block vs. inline
The Text component allows you to specify whether you want block
or inline
text.
Colors
You can specify which color you want for your text. Most colors change in dark mode, but light
and dark
are available when no switch is desired.
Overflow & truncation
Gestalt provides utility options to deal with text overflow.
Sizes
You can apply size
options to define the size of the text. These font sizes follow those available through our Design Tokens. If your text needs to be a semantic heading (H1-H6), use Heading instead.
Styles
There are multiple styles, such as bold and italic, that we can attach to the Text component.
Title
The title
attribute on a <div>
can be used to show the full text of a truncated string on hover. That attribute is populated automatically when the text is truncated using lineClamp
, as long as children
is a string.
If children
is a React.Node
(e.g. when using Link), use the title
prop to manually set the title
attribute.
Refs
Don't use ref
to manipulate the underlaying HTML div or span elements. Use ref
to only read HTML attributes. For example, a valid use case can be detecting truncation. The example below illustrates a case where detecting truncation allows rendering links contained within Text.
Writing
- Keep text in UI components short and clear
- Use Sentence case for UI labels
- Use long text labels that could end up truncating or causing space issues when translating to other languages
- Use Title Case or ALL CAPS in UI labels
- Use ALL CAPS for paragaph text unless referring to a product or other entity that uses that style
Related
Heading
Heading allows you to add H1–H6 level text on a page. They are generally placed underneath a PageHeader, and provide you with a way to create a logical text hierarchy.
Typography guidelines
A run-down on our typographic foundations, with some guidelines for using Heading and Text components together in products.
Design tokens
Values for text sizes, weights, families and colors.
Link
Used as a text-only navigational element. Links usually appear within or directly following a paragraph or sentence.
Component quality checklist
Quality item | Status | Status description |
---|---|---|
Figma Library | Ready | Component is available in Figma across all platforms. |
Responsive Web | Ready | Component is available in code for web and mobile web. |
iOS | Component is not currently available in code for iOS. | |
Android | Component is not currently available in code for Android. |