# Keep an HTML report readable when text is enlarged

Canonical: https://githtml.com/guides/zoom-and-reflow-html-reading
Published: 2026-09-26
Publisher: WaveTech LLC / gitHtml

Let ordinary text reflow within the available width and allow containers to grow vertically. Avoid zoom restrictions, fixed-height text panels, and layouts that require a desktop-sized canvas. Review enlarged text and narrow widths separately, keeping genuinely two-dimensional material such as tables contained without making every paragraph scroll sideways.

## Look for content loss, not just overflow

A layout can appear neat while hiding words. Fixed-height callouts, clipped navigation labels, and absolutely positioned captions may lose information as text grows. Inspect the bottom of each constrained box and the boundaries between adjacent elements. The important question is whether the reader can still reach all content, not whether the original composition remains visually identical.

For a report, normal document flow is usually a strong starting point. Let headings wrap and panels expand. Use maximum widths to control long lines on large screens without imposing a minimum width on small ones. Avoid designing around the exact length of the current title; future revisions and translations will stress those assumptions.

## Handle exceptions locally

Some content genuinely benefits from two-dimensional presentation. A data table, diagram, or meaningful code layout may need additional horizontal space. Give that content an appropriate local treatment and keep the surrounding prose flexible. Do not use one wide table as a reason to force the entire report into a desktop-width wrapper.

When simplifying a layout for a narrow view, preserve information and reading order. Hiding caveats or evidence columns to make the page fit changes the report, not just its presentation. A concise summary can accompany a full table, but it should not silently replace the only available limitations.

## Run a focused enlargement review

Use the actual exported document and inspect a representative mix of content. A short introduction may pass while a long link label or warning fails. The WCAG reflow guidance provides a specific evaluation framework; a quick manual check is useful but should not be described as full conformance testing.

1. Keep the viewport free of unnecessary zoom restrictions.
2. Enlarge text and inspect headings, captions, links, and warnings.
3. Narrow the viewing area and check ordinary paragraphs for sideways reading.
4. Remove fixed heights that clip text.
5. Check the last row and column of wide content for reachability.
6. Record the environment and settings used so the review can be reproduced after the next export.

## Sources and further reading

- [W3C: understanding reflow](https://www.w3.org/WAI/WCAG22/Understanding/reflow.html)
- [W3C: understanding resize text](https://www.w3.org/WAI/WCAG22/Understanding/resize-text.html)

## Related guides

- [Build a heading outline that makes a long report navigable](https://githtml.com/guides/heading-hierarchy-readable-html)
- [Use landmarks to separate navigation from the report body](https://githtml.com/guides/document-landmarks-for-html-reading)
- [Write screenshot alternatives that explain the useful information](https://githtml.com/guides/alt-text-for-document-screenshots)
- [Describe architecture diagrams as relationships, not shapes](https://githtml.com/guides/text-descriptions-for-architecture-diagrams)

Editorial approach: https://githtml.com/guides/about