> ## Documentation Index
> Fetch the complete documentation index at: https://patterns.heurilens.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Readability

> A measurable UX pattern where users struggle to process content due to density, structure, or typographic friction.

## Readability as a UX signal

Readability problems are rarely noticed consciously.\
Users do not think *“this text is hard to read”* —\
they simply **stop processing information**.

This makes readability one of the most silent,
yet most damaging UX failure patterns.

<Note>
  Readability is not about writing quality.\
  It is about **how efficiently information is absorbed**.
</Note>

## What breaks when readability fails

When readability breaks, content is still visible —\
but **meaning is delayed or lost**.

Common failure modes:

* information is buried in long paragraphs
* headings do not guide scanning
* text blocks feel visually heavy
* emphasis is unclear or overused

## Observable user behavior

> “Users don’t scroll because they’re curious.\
> They scroll because they’re searching for clarity.”

Behavioral traces linked to readability failure:

* repeated up/down scrolling
* partial reading (skipping sections)
* long dwell time without interaction
* delayed decisions after content exposure

These are **processing issues**, not motivation issues.

## Product-level signals

At the interface level, readability breakdowns often appear as:

* paragraphs exceeding comfortable line length
* inconsistent spacing between text blocks
* headings visually similar to body text
* low contrast between text and background
* dense content above the fold

<Frame>
  <img src="https://mintcdn.com/heurilens/gl-jdYlebDR0ByAq/images/readability.png?fit=max&auto=format&n=gl-jdYlebDR0ByAq&q=85&s=517a31bc4c60eab3cc5684bdb2923749" alt="A measurable UX pattern where users struggle to process content due to density, structure, or typographic friction." className="rounded-xl" noZoom={true} width="1200" height="466" data-path="images/readability.png" />
</Frame>

## How Heurilens detects readability issues

Instead of judging text quality, Heurilens evaluates **processing effort**.

<AccordionGroup>
  <Accordion title="Text density & line length" icon="align-left">
    Measures paragraph length and character count per line
    to identify scanning fatigue risks.
  </Accordion>

  <Accordion title="Scannability structure" icon="list">
    Checks whether headings, spacing, and emphasis
    create a clear reading path.
  </Accordion>
</AccordionGroup>

## Example output from Heurilens

<Card title="Readability Breakdown Detected" icon="triangle-exclamation">
  Users require increased cognitive effort to extract key information.

  Dense paragraphs and weak visual separation reduce
  scanning efficiency and delay comprehension.
</Card>

## Example fix generated by Heurilens

```css theme={null}
/* Improve reading comfort */
.content {
  max-width: 68ch;
}

.content p {
  line-height: 1.6;
  margin-bottom: 1rem;
}

.content h2 {
  margin-top: 2.5rem;
}
```

<Tip> This fix does not change content — it reduces the **effort required to process it**. </Tip>

## Why this pattern matters

Readability failures do not cause immediate exits. They cause slow disengagement.

Users stay longer, but:

understand less

miss key points

hesitate to act

This makes readability issues hard to detect without measurement.

## Related patterns

<CardGroup cols={2}>
  <Card title="Visual Hierarchy" icon="layer-group" href="https://patterns.heurilens.com/modules/core-ux/visual-hierarchy"> When text lacks clear emphasis and priority. </Card>
  <Card title="Cognitive Load" icon="brain"> When information density exceeds processing capacity. </Card>
</CardGroup>

<Card title="Detect readability issues on your product" icon="sparkles" href="https://heurilens.com/auth/signup">
  Analyze a page and see where content becomes difficult to process.
</Card>
