# Typography

## Typography and Accessibility

Good typography ensures that text is pleasant to read and that the content appears clearly structured. Here are some important points to consider:

1. **Clear Hierarchy**
   * The most important heading (H1) should appear only once per page.
   * This is followed by H2, H3, etc. – always in a logical order.
   * Avoid jumps, i.e., don't jump directly from H1 to H4.
2. **Appropriate Font Sizes**
   * Headings should be significantly larger than the body text.
   * Body text shouldn't be too small – 14px to 18px is ideal.
   * Very small text (e.g., on buttons) should remain easy to read.
3. **Good Readability**
   * Lines shouldn't be too long – 50 to 75 characters per line is optimal.
   * There should be enough space between lines to make the text appear airy.
   * Text should be divided into meaningful paragraphs to facilitate readability.
4. **Consider contrast**
   * The text should stand out clearly from the background (e.g., dark text on a light background).
   * Too little contrast (gray text on a gray background) makes reading difficult.
   * Color highlights should be used sparingly.
5. **Choose the right font**
   * Don't use too many different fonts – no more than two or three.
   * Serif fonts (with small decorations) have a classic and elegant look, but are more suitable for print.
   * Sans serif fonts are more modern and better for digital content.
6. **Highlight important content**
   * You can bold important terms, but not too many at once.
   * Italics should be used sparingly because they are harder to read.
   * Use underlines only for links to avoid confusion.
7. **Maintain consistency**
   * The same fonts and sizes should be used consistently throughout a document or website.
   * A consistent style appears more professional and ensures a pleasant reading experience.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://themedocs.zenit.design/en/faq/accessibility/typography.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.