Text clipped out of view

How the text is hidden

Two families. The total clip is clip-path: inset at 100% or more, and the legacy clip: rect(0,0,0,0) idiom — normally written with a 1px width and height, which is the point, because it defeats a zero-size check by not being zero while the clip does the concealing. The second family is the clamp: overflow:hidden or clip together with -webkit-line-clamp/line-clamp, or with a max-height/height, which renders a fixed number of lines and crops the rest.

Why a model still reads it

Clipping happens at paint. The full string is in the DOM either way — for the clamp case, a reader sees the opening lines and a model reads the whole passage.

What we do about it

The total-clip forms set the run's reason to clipped directly. The clamp form does not mark anything invisible on its own; instead it converts the declared line count into a character budget using limits.clampMaxCharsPerLine from the rule pack, walks the runs inside the clamped span in document order, leaves everything up to the budget visible, and marks the remainder clipped — splitting a run that straddles the budget so the visible head stays visible and the excerpt a reviewer reads is the hidden tail alone. The rule fires at high with action flag, requires the accessibility flag to be clear so the .sr-only idiom is claimed by the accessibility rule instead of double-reported, and is guarded by the container clause. Text is reported and retained; containerVisibility is never.

How often it fires

0% of 400 real pages from 400 distinct hosts (Common Crawl) — pages, not documents, measured 2026-08-21.

This is an alert-volume number and nothing else. It says how often the alarm sounds on documents as found — not how often it is right, and not whether what it found was harmless. Documents as found may themselves carry concealment. Read it against the population named above rather than as a property of documents in general.

Seen in the wild

Every recorded incident, across all techniques.