Content Reflow
Content reflow fits a page into a narrow space without losing content or functions. Most reading should not need two-way scrolling.
320 CSS px / 400% zoom -> wrap + stack + no lost content or page-wide x-scroll3 columnsNarrow1 columnmin-inline-size: 0overflow-x:auto320 CSS px / 400% zoom -> wrap + stack + no lost content or page-wide x-scrollA11YAnother example
At 400% zoom, cards stack into one column and text wraps. A wide table scrolls only inside its own region.
Main parts
- 01Narrow viewport
- 02Wrapped text
- 03Stacked regions
- 04Growing controls
- 05Local overflow exception
- 06No lost function
Use it when
Test at a width equal to 320 CSS pixels. Let text wrap, controls grow, and page sections stack.
Do not use it when
Do not hide or truncate important content at high zoom. Avoid horizontal scrolling across the whole page.
Name used in code
320 CSS px / 400% zoom -> wrap + stack + no lost content or page-wide x-scroll Before you ship
Before release, check the page structure, keyboard access, visible focus, contrast, and zoom. Also check loading, empty, error, success, cancel, and reduced-motion states.
Outcome: Use Content Reflow to solve this user need without losing the current context. User context: At 400% zoom, cards stack into one column and text wraps. A wide table scrolls only inside its own region. Recommended pattern: Content Reflow. Why it fits: Test at a width equal to 320 CSS pixels. Let text wrap, controls grow, and page sections stack. Do not use it when: Do not hide or truncate important content at high zoom. Avoid horizontal scrolling across the whole page. Product requirements: Define the default, loading, empty, error, success, and recovery states. Keep user input. Give clear feedback after every action. Accessibility and resilience: Use semantic HTML, full keyboard access, and visible focus. Make the layout work when zoomed and support reduced motion. Follow the project’s current rules. Do not add a new UI library unless the project already uses it. Acceptance criteria: The main task works with keyboard only and at 320px width. Focus and status changes are announced. Check loading, failure, retry, cancel, and reduced-motion paths. Evidence and limits (evidence boundary): The standard covers only the listed scope. It does not choose the visual style, product decision, or Vibulary example. Unknowns to confirm: Product wording, data source, analytics events, supported devices and languages, and platform limits.
Check this request
Review the current use of Content Reflow. Definition: Content reflow fits a page into a narrow space without losing content or functions. Most reading should not need two-way scrolling. Release checks: Before release, check the page structure, keyboard access, visible focus, contrast, and zoom. Also check loading, empty, error, success, cancel, and reduced-motion states. Before changing code, report the evidence you found, gaps, severity, and the smallest safe fix.