Web design and digital-business ideas grounded in real tasks.

Your page should still work when a reader increases text spacing

A web designer comparing a normal and widely spaced text layout on two screens.
AI-generated photographic illustration; not documentary photography.

A card looks tidy with its default font settings. Increase the line spacing, however, and the final sentence disappears behind a fixed-height container. The reader has not broken the page by making it easier to read; the layout failed to accommodate the adjustment.

WCAG 2.2 success criterion 1.4.12 addresses this problem. For applicable markup and writing systems, content and functionality should remain available when users change line height, paragraph spacing, letter spacing and word spacing to the specified values. It does not require every site to use those values as its default visual design.

Test the combined change

The criterion specifies a line height of at least 1.5 times the font size, paragraph spacing of twice the font size, letter spacing of 0.12 times the font size and word spacing of 0.16 times the font size. Apply the changes together with an appropriate testing tool or user stylesheet, then inspect the page rather than checking only whether the CSS was accepted.

Start with places where space is constrained: navigation items, card summaries, buttons, badges, form labels and validation messages. A paragraph that expands correctly does not prove that the checkout button or error explanation remains usable.

Repair the constraint that causes the loss

In an illustrative product card, the text may need to grow vertically while the surrounding layout adapts. Increasing one fixed height can hide the problem for one sample and leave it in place for a longer title or translated description. Review the container’s sizing and overflow behaviour instead.

Check keyboard access after the adjustment too. A control that remains in the document but is visually covered by another element is not a successful result. Retest both the adjusted and default views after changing the layout.

Record the page, component and lost content in a reproducible bug report. Include the spacing settings and viewport so another developer can see the same failure. This makes the issue easier to fix than a general comment that “the page looks wrong with accessibility settings.”

Readers bring different visual needs to the same content. A flexible layout lets those preferences change the presentation while preserving the task.