- Level
- AA
- Since
- WCAG 2.1
- Entries
- 10 / 193
1.4.10 Reflow
A page has to work in a viewport 320 CSS pixels wide without making the reader scroll both down and sideways.
/ What it requires
People who magnify the screen need the page to rearrange itself, not just grow. At 400 percent zoom a desktop window 1280 pixels wide behaves like a viewport of 320 CSS pixels, the width of a small phone. If the layout keeps its desktop width, every line runs off the screen and has to be read by scrolling right and back again, sentence after sentence. Content is also lost when wide blocks are clipped or pinned bars cover most of the view.
The criterion requires content to be presented without loss of information or functionality, and without scrolling in two dimensions, at a width of 320 CSS pixels for pages that scroll vertically and a height of 256 CSS pixels for content that scrolls horizontally. It exempts parts that need a two-dimensional layout for their use or meaning: maps, diagrams, video, games, data tables and interfaces that keep a toolbar in view during editing. Those parts may scroll both ways; the page around them may not.
/ How pages fail it
- The layout has a fixed width in pixels, so the page scrolls sideways at 400 percent zoom or on a narrow screen.
- The page has no viewport meta tag, so mobile browsers render it at desktop width and shrink it.
- A long URL, a wide image or a preformatted block pushes the page wider than the viewport.
- Content that no longer fits is clipped by overflow: hidden, so text or controls disappear instead of wrapping.
- A sticky header, a cookie banner and a chat widget together cover most of a viewport 320 pixels wide.
/ How to check it yourself
- Set the browser window to 1280 pixels wide and zoom to 400 percent with Ctrl and plus. Scroll down the whole page and watch for a horizontal scrollbar.
- Or open the developer tools, switch to the responsive mode and set the viewport to 320 by 256 pixels.
- Open every menu, dialog, form and accordion at that size and check that nothing is cut off and every control can still be reached.
- Where something scrolls sideways, decide whether it is an exempt part such as a data table or a map. If the whole page scrolls with it, it is not.
- View the page source and confirm that the head contains a viewport meta tag.
/ How to fix it
- Add meta name="viewport" content="width=device-width, initial-scale=1" to the head.
- Replace fixed width values with max-width and percentages, and build columns with flex-wrap: wrap or with a grid using auto-fit and minmax().
- Set max-width: 100% on img, video and iframe, and overflow-wrap: anywhere on text that can hold long strings.
- Wrap wide tables and code blocks in a container with overflow-x: auto, so they scroll inside their own box.
- In a narrow viewport switch sticky headers and banners to position: static, or reduce their height.
/ What our scanner checks
The static pass checks one thing here: whether the page source contains a viewport meta tag, and it reports the page when the tag is missing. It does not load the page at 320 pixels, so sideways scrolling, clipped content and oversized sticky bars go undetected. A missing tag is a strong hint that the layout will not reflow on a phone, not a measurement of it.
/ Who fails it, in our own measurements
| Body | Sector | Instances | Score |
|---|---|---|---|
| Federal Aviation Administration | transport · US | 1 | 14 |
| Gorzów Wielkopolski | city · PL | 1 | 6 |
| Kielce | city · PL | 1 | 71 |
| Miami-Dade County | government · US | 1 | 20 |
| National Weather Service | government · US | 1 | 34 |
| New York Public Library | culture · US | 1 | 24 |
| Sejm RP | government · PL | 1 | 9 |
| Social Security Administration | government · US | 1 | - |
| Sąd Najwyższy | government · PL | 1 | 14 |
| Zarząd Transportu Miejskiego Warszawa | transport · PL | 1 | 77 |
One page per body, measured by automated checks on a weekly schedule. Any body that has fixed something since the last sweep will show it at the next one, and every entity page carries a right of reply.
/ Questions about this criterion
How do I test reflow at 400 percent zoom?
Make the browser window 1280 CSS pixels wide, then zoom in to 400 percent. The viewport is now 320 CSS pixels wide, which is the size the criterion names. Go through the page from top to bottom, opening menus and forms on the way. Apart from exempt parts such as data tables and maps, nothing should need horizontal scrolling and nothing should disappear.
Why does WCAG use 320 CSS pixels?
Because 320 CSS pixels is what remains of a viewport 1280 pixels wide at 400 percent zoom, and it is also the width of a small phone held upright. The same reasoning gives 256 CSS pixels, a viewport 1024 pixels high at 400 percent, for content that scrolls horizontally. A responsive layout that works on a small phone usually meets both.
Do data tables have to reflow?
No. The criterion names data tables as content that needs a two-dimensional layout, so a table may scroll horizontally. The exemption covers the table, not the page: put it in a container with its own scrollbar, so the text around it still fits the viewport. The content of each cell should still wrap, and a table used only for layout is not exempt.
