# Reflow: Content That Fits at 400% Zoom

Source: https://allyway.ai/glossary/reflow

Reflow is WCAG success criterion 1.4.10. Content must work without loss of information or functionality and without scrolling in two directions at a width equal to 320 CSS pixels – or a height of 256 CSS pixels for horizontally scrolling content.

Reflow is the WCAG requirement that a page rearranges itself into a narrow layout when someone zooms in, instead of forcing them to scroll left and right on every line. It lets people with [low vision](https://allyway.ai/glossary/low-vision) enlarge a page to 400% and still read it like a normal column of text. A responsive site gets most of the way there – the rest is long words, wide tables and fixed boxes.

## What it means

[WCAG 1.4.10 Reflow](https://www.w3.org/WAI/WCAG22/Understanding/reflow.html) is a Level AA criterion of [WCAG 2.2](https://allyway.ai/regulations/wcag-2-2). Content must be presented without loss of information or functionality, and without two-dimensional scrolling, at these sizes:

| Content | Size to test | Equivalent |
|---|---|---|
| Scrolls vertically (most web pages) | Width of 320 CSS pixels | 1280 px wide window at 400% zoom |
| Scrolls horizontally (e.g. vertical writing) | Height of 256 CSS pixels | 1024 px high window at 400% zoom |

The math is simple: 1280 ÷ 4 = 320 and 1024 ÷ 4 = 256.

**Exception:** parts of the content that need a two-dimensional layout for usage or meaning. W3C lists maps and diagrams, video, games, presentations, data tables and interfaces that must keep a toolbar in view. A data table may scroll sideways inside its own container – but the heading, search field and pagination around it still have to reflow.

Why it matters: W3C explains that scrolling in two directions makes people lose their place on every line and costs physical and cognitive effort. When whole lines stay visible, readers only scroll in the reading direction. Reflow works together with [resize text](https://allyway.ai/glossary/resize-text): 1.4.4 asks for 200% text size, 1.4.10 for a usable layout at 400% zoom.

> **Tip:** > **Test with browser zoom, not a phone emulator**
> Set the window to 1280 px wide and zoom to 400%. The browser then gives the page a 320 CSS pixel layout – the same test W3C describes.

W3C's failure F102 covers a common shortcut: content or functions that simply disappear in the narrow layout (for example a hidden "Compare" button) are not a pass.

## Examples

```html title="Example"
<style>
  /* Good: columns stack on narrow screens */
  .cards { display: grid; grid-template-columns: repeat(auto-fit, minmax(16rem, 1fr)); gap: 1rem; }

  /* Good: long URLs and words wrap instead of widening the page */
  .content { overflow-wrap: anywhere; }

  /* Good: images never exceed their container */
  img { max-width: 100%; height: auto; }

  /* Good: a wide data table scrolls inside its own box */
  .table-wrap { overflow-x: auto; }

  /* Bad: fixed width forces horizontal scrolling */
  .page { width: 1200px; }
</style>
```

**Do:** Do

Build with flexible grids and flexbox (W3C techniques C31, C32), wrap long strings (C33), let form labels and fields shrink with `max-width` (C38) and keep sticky headers small or unfixed on narrow screens.

**Don't:** Don't

Set fixed pixel widths on page containers, hide content or controls at small widths to make the layout fit, or keep a large fixed header and cookie bar that cover half the zoomed screen.

## How to check reflow



## Questions

Q: What is reflow in accessibility?
A: Reflow means content adapts to a narrow viewport – 320 CSS pixels wide – so people who zoom to 400% can read without scrolling horizontally. It is WCAG success criterion 1.4.10 at Level AA.

Q: Why 320 pixels?
A: W3C chose 320 CSS pixels because it equals a 1280 px wide desktop window at 400% zoom. It is also close to the width of small phones, so a site that passes works on mobile too – a core part of [mobile accessibility](https://allyway.ai/glossary/mobile-accessibility).

Q: Are data tables allowed to scroll horizontally?
A: Yes. Data tables are an example of content that needs a two-dimensional layout. Put the table in its own scrollable container; the rest of the page must still reflow.

Q: Is a responsive website automatically compliant with reflow?
A: Not always. Common problems in responsive themes are long words or URLs, fixed-width embeds, sticky headers that take most of the zoomed screen and content hidden at small breakpoints.

Q: What is the difference between reflow and resize text?
A: Resize text (1.4.4) requires that text can be enlarged to 200% without losing content. Reflow (1.4.10) goes further: the whole page must work at 400% zoom without two-dimensional scrolling.
