Category: Visual and Media Accessibility

Text Spacing

Also known as: WCAG Success Criterion 1.4.12, Success Criterion 1.4.12 Text Spacing

Simply put

Text Spacing refers to the ability of users to adjust the space between lines, paragraphs, letters, and words in text without losing content or breaking how a page works. It helps people who need more spacing to read comfortably, such as some users with low vision or dyslexia. It is addressed by a WCAG success criterion commonly cited at conformance Level AA.

Formal definition

Text Spacing is defined by WCAG Success Criterion 1.4.12, introduced in WCAG 2.1 at conformance Level AA. It requires that no loss of content or functionality occurs when a user overrides text spacing to at least the following values (with no other style property changed): line height (line spacing) of at least 1.5 times the font size, spacing following paragraphs of at least 2 times the font size, letter spacing (tracking) of at least 0.12 times the font size, and word spacing of at least 0.16 times the font size, per the W3C Understanding document. In implementation, these properties commonly map to CSS such as line-height, letter-spacing, word-spacing, and paragraph margins. Note that meeting this criterion is one aspect of accessibility and does not by itself guarantee overall usability or legal compliance; manual and assistive technology testing remain necessary, and this entry is not legal advice.

Why it matters

Readable text is foundational to using the web, and the ability to increase spacing between lines, paragraphs, letters, and words can make the difference between content that is legible and content that is overwhelming. Some people with low vision, dyslexia, or other reading-related needs adjust text spacing through browser settings, extensions, or custom stylesheets so they can process text more comfortably. When a page is built with fixed or rigid layouts, those adjustments can cause text to overlap, get cut off, or push controls out of reach, effectively locking out users who depend on spacing changes.

Text Spacing, addressed by WCAG Success Criterion 1.4.12 at Level AA, focuses on ensuring that when users override spacing to the specified values, no content or functionality is lost. Rather than requiring authors to provide a spacing control themselves, the criterion asks that a page remain usable when users apply their own spacing preferences. This supports personalization and respects the reality that no single fixed layout works for everyone.

Meeting this criterion is one aspect of an accessible experience and does not by itself guarantee overall usability or legal compliance. Automated tools may flag some spacing-related layout problems, but manual review and testing with assistive technologies remain necessary to confirm that content and functionality survive user spacing adjustments. This entry is not legal advice; requirements evolve through regulation and case law, and organizations should consult qualified counsel for their specific obligations.

Who it's relevant to

Front-end developers and engineers

Developers implement the layouts and CSS that determine whether text spacing overrides break content. Building with flexible containers that expand with increased line-height, letter-spacing, word-spacing, and paragraph margins helps ensure no content or functionality is lost when users apply their own spacing values.

UX and visual designers

Designers influence whether a layout can accommodate additional spacing without clipping or overlap. Anticipating that users may increase spacing to the values specified in SC 1.4.12 helps avoid fixed-height containers and tight layouts that cannot adapt.

Accessibility testers and QA teams

Testers verify conformance by applying the specified spacing values, commonly using browser extensions or bookmarklets, and checking that content remains visible and functionality operable. Because automated tools detect only a portion of issues, manual and assistive technology testing are important for this criterion.

Readers who rely on custom spacing

People with low vision, dyslexia, or other reading-related needs may adjust spacing to read more comfortably. This criterion is intended to keep pages usable when they do so, though individual needs vary and meeting the criterion does not guarantee an optimal experience for every user.

Compliance officers and accessibility leads

Those responsible for conformance targets should understand that SC 1.4.12 is commonly cited at Level AA and was added in WCAG 2.1. Meeting it is one part of a broader accessibility effort and does not by itself ensure overall usability or legal compliance; consult qualified legal counsel regarding specific obligations.

Inside Text Spacing

Text Spacing Success Criterion (WCAG 1.4.12)

A Level AA success criterion introduced in WCAG 2.1 that requires content to remain readable and functional when users override text spacing properties, with no loss of content or functionality.

Line height (line spacing)

The vertical spacing between lines of text. Under the criterion, content should support a line height of at least 1.5 times the font size without breaking.

Spacing following paragraphs

The space below a paragraph. The criterion generally references support for spacing of at least 2 times the font size following paragraphs.

Letter spacing (tracking)

The horizontal spacing between characters. The criterion commonly references support for letter spacing of at least 0.12 times the font size.

Word spacing

The spacing between words. The criterion commonly references support for word spacing of at least 0.16 times the font size.

User-applied styles

The criterion concerns spacing values that a user sets (for example, via a browser extension or custom stylesheet), not necessarily the author's default presentation. Content must adapt to these overrides without clipping, overlap, or loss of function.

Common questions

Answers to the questions practitioners most commonly ask about Text Spacing.

Does the text spacing success criterion require my page to use specific spacing values by default?

No. WCAG 2.1 Success Criterion 1.4.12 (Text Spacing, Level AA) does not require your default styling to use particular spacing values. Instead, it requires that no loss of content or functionality occurs when a user overrides text spacing up to certain metrics. You may design with whatever spacing you prefer, provided the content still works when users apply the specified spacing adjustments themselves, typically through a browser extension, bookmarklet, or custom stylesheet.

If my content passes this criterion, does that mean the text is comfortably readable for everyone?

Not necessarily. Meeting Success Criterion 1.4.12 confirms that content and functionality survive user-applied spacing changes without clipping, overlap, or loss. It does not guarantee that the default presentation is optimal or comfortable for all readers. Conformance to a success criterion addresses a specific measurable requirement and is distinct from broader usability. Manual review and testing with real users and assistive technology remain important, and this guidance is not legal advice.

What spacing values does WCAG 2.1 reference for this criterion?

Success Criterion 1.4.12 references the ability to set line height (line spacing) to at least 1.5 times the font size, spacing following paragraphs to at least 2 times the font size, letter spacing (tracking) to at least 0.12 times the font size, and word spacing to at least 0.16 times the font size, without loss of content or functionality. Consult the current W3C text of the criterion and its understanding documents for the authoritative wording, as details may be clarified over time.

How can I test whether my content meets this criterion?

A common approach is to apply the referenced spacing values through a custom stylesheet or a browser bookmarklet built for this purpose, then review the page for clipped text, overlapping elements, hidden content, or broken controls. Because these issues are largely visual and contextual, manual inspection is generally required; automated tools detect only a portion of potential problems. Test across the layouts, components, and viewport sizes your content uses.

What CSS practices tend to help content withstand user-applied text spacing?

Practices often cited include avoiding fixed heights on text containers, allowing containers to expand with content, and using flexible or relative units so that layouts reflow rather than clip. Designing components to accommodate larger amounts of text generally reduces the risk of overlap or truncation when users increase spacing. Verify the actual behavior through testing, since outcomes depend on your specific implementation.

Does this requirement apply to text rendered inside images?

The criterion concerns text that users can adjust, which generally means text rendered as actual text that responds to style overrides. Text baked into images does not respond to user spacing adjustments, and other WCAG provisions address images of text separately. Where feasible, presenting content as real, styleable text supports both this criterion and broader accessibility goals.

Common misconceptions

The Text Spacing criterion requires authors to design their pages with these exact spacing values by default.

The criterion generally addresses whether content still works when a user applies these spacing values, rather than mandating that authors use them as the default presentation. The focus is on the absence of content loss or broken functionality when spacing is overridden.

Text Spacing has always been part of WCAG.

Success Criterion 1.4.12 Text Spacing was added in WCAG 2.1 and is not present in WCAG 2.0. It is designated Level AA, which is the level most commonly cited as a conformance target.

Passing an automated check for text spacing means the page is fully accessible and legally compliant.

Automated testing detects only a portion of potential issues, and text spacing behavior in particular often needs manual verification. Meeting this criterion does not by itself guarantee an accessible experience for all users or immunity from legal claims.

Best practices

Test your content by applying line height of 1.5x, paragraph spacing of 2x, letter spacing of 0.12x, and word spacing of 0.16x the font size, and confirm no text is clipped, overlapped, or cut off.

Avoid fixed-height containers for text; use flexible layouts that expand to accommodate increased spacing without hiding or truncating content.

Verify that interactive elements such as buttons and links remain fully visible and operable when user spacing overrides are applied.

Combine automated checks with manual testing and assistive technology review, since spacing-related breakage is frequently missed by automated tools alone.

Test across multiple browsers and viewport sizes, as spacing overrides can interact differently with responsive breakpoints.

Treat WCAG 2.1 Level AA (including 1.4.12) as a commonly cited target, and consult qualified legal counsel and current agency guidance to understand how it applies to your specific obligations.