Chunking information for readability

Humans have limited working memory. Long, unstructured blocks of text or data quickly overwhelm users, leading to frustration and missed information.

By chunking content into sections, lists, and visual groups, you align with how people naturally process information. This makes reading, decision-making, and task completion smoother.

Guidelines for chunking information to improve readability and comprehension.

Break content into logical sections

Divide long content into meaningful groups with headings or dividers. Each section should focus on a single idea.

References:

• Chunking content for scannability – Nielsen Norman Group
• Cognitive accessibility – WebAIM

Use headings and subheadings

Headings guide readers and screen readers alike. They improve orientation and scanning.

References:

• WCAG 2.4.6: Headings and labels
• Content design – Sarah Richards

Present lists instead of long paragraphs

Bulleted or numbered lists make items easier to scan and remember compared to dense text.

References:

• Writing for the web – Nielsen Norman Group

Keep paragraphs short and focused

Keep paragraphs to 2–4 sentences for readability, especially on mobile screens.

References:

• WCAG 3.1.5: Reading level

Support with visual grouping and spacing

White space, borders, and background color can visually separate chunks and reduce cognitive load.

Combine text with visuals when useful

Diagrams, icons, or images can reinforce meaning and break monotony when paired with text.

References:

• Universal principles of design – William Lidwell, Kritina Holden, Jill Butler

Frequent mistakes when chunking information.

Presenting long unbroken walls of text

Dense text blocks overwhelm users and hide key points.

Using vague or missing headings

Without clear headings, users and assistive technologies can’t navigate effectively.

Mixing unrelated topics in one section

Each chunk should cover one idea to avoid confusion.

Overloading lists with too many items

Group or paginate long lists to keep them scannable.

Ignoring spacing, making chunks blend together

Insufficient whitespace reduces clarity and increases cognitive load.

Key takeaways for chunking information.

• Break content into clear, logical sections with headings.
• Use lists and short paragraphs to support scanning.
• Apply whitespace and visual grouping for clarity.
• Pair text with visuals when helpful.
• Avoid overwhelming users with dense, unstructured content.

Chunking respects human memory limits and reading behavior, making information more accessible, engaging, and easy to act upon.

Scenario: Long-form content page

Use when designing articles, documentation, guides, or policy pages with substantial text that users scan rather than read linearly.

You are a UX-focused design agent. Design the content structure for a long-form content page about [topic: API documentation / onboarding guide / policy document].

Rules:
- Heading hierarchy: one H1, H2 for major sections (3-5), H3 for subsections
  Headings describe content — never vague or decorative
  Sentence case: "Getting started with authentication"
  Not: "Getting Started With Authentication"

- Paragraphs: 3-5 sentences maximum, one idea per paragraph
  Start with the most important information

- Lists:
  Bullets: 3+ items of equal weight without natural order
  Numbers: sequential steps or ranked items
  Keep list items parallel in structure

- Table of contents: add for pages longer than 1500 words

- Callout boxes (use sparingly — max 1 per 300 words):
  Warning / Tip / Note — always include a text label, not just color

- Code: always in pre and code blocks with syntax highlighting and a copy button

- Whitespace: generous spacing between sections — at least 1.5x line height

Accessibility:
- Heading levels sequential — never skip from H2 to H4
- Lists: use ul or ol — never manually typed dashes or numbers
- Code blocks: use pre and code elements

Constraints:
- Never use heading elements for visual styling only
- Never write paragraphs longer than 5 sentences
- Never create lists with fewer than 3 items — write as prose instead