Inline Text Spacing Must Be Adjustable: Support User Preferences

In one paragraph

Inline text spacing must be adjustable with custom stylesheets identifies restrictive style declarations within this rule's narrow scope. Remove unnecessary resistance to user preferences and test the layout after spacing changes. WCAG does not require every page to ship those settings as its default design. An author-inline important declaration can defeat common injected author styles, but true user-origin important styles have different cascade precedence.

Why it matters

WCAG 1.4.12 requires no loss of content or functionality when supported text-spacing properties are adjusted to the specified values without changing other style properties. It is an adaptability requirement, not a demand for a particular default typographic appearance.

The tested settings include line height of at least 1.5 times font size, paragraph-following spacing of at least 2 times font size, letter spacing of at least 0.12 times font size, and word spacing of at least 0.16 times font size. Language and script exceptions apply where a property is not used.

A reader's method can be a user stylesheet, extension, bookmarklet, or browser feature. Those mechanisms do not always inject the same cascade origin. Avoid claiming author inline important can never be overridden by any user mechanism or that every external test-tool limitation is automatically a site failure.

How WebAuditOS evaluates this finding

The supplied avoid-inline-spacing rule inspects applicable inline important declarations for letter spacing, word spacing, and selected wrapping line-height cases, comparing its computed thresholds with font size. It has documented keyword exceptions and does not cover every stylesheet rule.

Serious impact maps to high severity. The rule does not perform a complete four-property layout test, including paragraph spacing and resulting clipping. A pass cannot establish that increased spacing leaves all text, controls, and functions available.

How to fix it

1. Inspect the actual inline declaration and the component that emits it. Determine whether important is necessary or a styling workaround that can be removed or redesigned.
2. Prefer maintainable normal author styles where appropriate. Moving a declaration into a stylesheet may help common injected overrides, but does not by itself prove the final cascade or layout supports user settings.
3. Apply all relevant criterion settings in a controlled test and verify their computed effect. Do not assume a pasted bookmarklet succeeded when an important rule still wins.
4. Check line height, paragraph spacing, letter spacing, and word spacing together where the writing system uses them. Testing only a generous paragraph gap misses the other requirements.
5. Inspect headings, navigation, buttons, validation text, labels, tables, and fixed-height cards. Look for clipped words, overlapping elements, lost controls, and content that becomes inaccessible after wrapping.
6. Fix restrictive dimensions and layout assumptions instead of shrinking the user's text back down. An ellipsis can be appropriate only when the complete content remains available through a suitable mechanism.
7. Repeat at representative widths, languages, states, and translated text lengths. Combine the review thoughtfully with zoom and responsive tests without confusing their different criteria.
8. Rescan the inline-style warning and retain a manual spacing-adaptation test. Removing one important declaration does not validate every screen or justify advertising complete WCAG conformance.

What the fix can break

Increased spacing can reveal fixed-height assumptions or tightly positioned overlays. Repair those layouts rather than treating the preference as a user error.

A global important-removal change can alter unrelated component states. Scope the repair and verify styles and interactions before a broad rollout.

Do not add forced default spacing merely to make the checker happy if it damages language-specific typography. Support the applicable user adjustments and respect the criterion's script exceptions.

Questions

Must my default body text use all four values?

No. The requirement is that the relevant adjustments can occur without loss of content or functionality.

Does inline important defeat every user style?

No. Cascade origin matters; true user-origin important styles and injected author styles are not the same mechanism.

Does this rule test paragraph spacing and clipping?

Not completely. Its documented inline-property checks are narrower than a full adaptation assessment.

Which related checks help?

Review contrast, zoom, and the automation limits guide.

What severity does this get in the report?

High. An axe finding takes its severity from the impact axe reports for the element that failed, and the report maps critical and serious to high, moderate to medium, minor to low. This rule is declared serious in axe-core 4.13.0, so a failure arrives as high - which is why the panel above states a conformance level rather than a severity.