AccessLumens

WCAG 1.4.12

Text Spacing

Level AAWCAG 2.1

0

automated findings for 1.4.12, across our entire corpus

609 site scans and 941 PDF documents. No engine tests this criterion, ours included, so a site can pass every automated check and still fail it completely.

What it means and how to fix it

For what the criterion formally requires, read the W3C Understanding document.

The closest thing we can measure

Content forces side-to-side scrolling when zoomedreflow-horizontal-scroll-32030%

Each of these detects a specific, unambiguous failure that would also be a failure of 1.4.12. They give a floor, never a total, because they cannot see the cases that need judgement.

What this does not measureLimits of these figures, and where the corpus came from
  • Not directly testable on a web page. Related checks bound it, but cannot confirm it.
  • Not applicable to PDF documents in our checker.
  • These are five targeted cohorts, not a random sample of the web. Per-cohort rates are the figure to quote; the pooled rate is a convenience sample.
  • Denominators count sites that produced a result. Sites that were blocked or errored are excluded rather than counted as passing.
  • Occurrence counts are floors: the engine records at most 25 occurrences of a rule per page.
  • The EU and Indian cohorts retained only the primary success criterion per finding, so a rule mapping to several criteria contributes to one of them in those two cohorts and to all of them in the other three.
Cohorts in the corpus, with sites scanned and attempted
CohortScannedAttempted
Shopify DTC stores7575
US local government158221
US healthcare providers208218
EU e-commerce107170
Indian financial services6172

Corpus generated 2026-09-18.

Check your own site

A free scan runs the related checks that bound WCAG 1.4.12, but it cannot confirm it. Treat a clean result as the start of a manual review, not a pass.

Run a free scan

All accessibility rules and WCAG criteria