The self-scrolling logo strip can stand still.
The looping logo strip shows up on 82 of the 509 sites in the study and on 24 of the 63 sloppiest. WCAG asks for a way to pause it; a still row is almost always better.
A row of logos sliding forever under "Trusted by" is one of the first things an AI generates when it builds a landing page. It takes a few lines of CSS with @keyframes and infinite, and it animates without being asked.
Across the 509 sites in the November study, the signal "Auto-scrolling logo or phrase strip" in the Slop Score appears on 82. It is on 24 of the 63 sloppiest sites and 15 of the 167 most cared for: it separates less than other signals, but it turns up on one site in six.
What the Slop Score looks at
The signal fires when an element has an infinite animation that moves it at least 20 pixels and holds text or two or more logos or icons. The <marquee> tag counts too. An animation that spins an icon or pulses a dot doesn't count here: it looks for the strip that runs.
This is the typical shape:
.logos-track {
display: flex;
width: max-content;
animation: scroll 30s linear infinite;
}
@keyframes scroll {
to { transform: translateX(-50%); }
}What accessibility says
WCAG success criterion 2.2.2, "Pause, Stop, Hide", requires a mechanism to pause, stop or hide any content that moves, blinks or scrolls and meets three conditions: it starts automatically, lasts more than five seconds and is shown alongside other content. According to W3C, the reason is that continuous movement distracts people with cognitive disabilities and attention deficits.
A logo strip meets all three: it starts by itself, never ends and shares the page with other content. With no button or other way to stop it, it fails a level A criterion.
What the strip does, and what to use
The strip solves a real problem: there are more logos than fit in one row. But the logos that matter, the customers a visitor recognizes, are few. With five or six, a still row reads in a second; with twenty in motion, none of them gets read.
My rule: if the logos are real, keep them still and in a single color. If you have no customers to show, the section has to go, because a strip of generic names is worse than nothing.
/* Still strip: a row that wraps */
.logos {
display: flex;
flex-wrap: wrap;
gap: 24px 48px;
align-items: center;
}
.logos img { height: 28px; width: auto; }If the strip stays
If you prefer to keep the motion, MDN explains that prefers-reduced-motion detects whether a person asked their system to minimize non-essential motion, and that panning animations can trigger discomfort for people with vestibular disorders. With @media (prefers-reduced-motion: reduce) the animation turns off for them.
The <marquee> tag, for its part, is deprecated: MDN discourages it and suggests a CSS animation with transforms plus the reduced-motion media query. Pausing on hover helps, but a visible pause button is what covers keyboard and phone users.
/* If the strip stays, let people stop it */
.cinta { animation: correr 40s linear infinite; }
.cinta:hover, .cinta:focus-within { animation-play-state: paused; }
@keyframes correr { to { transform: translateX(-50%); } }
@media (prefers-reduced-motion: reduce) {
.cinta { animation: none; flex-wrap: wrap; }
}Ask your AI for it
For my site, remove every infinite animation that moves logos or phrases
(marquee, auto-scrolling carousel, keyframes with infinite and translateX).
Put the logos in a still row with flex-wrap, 24 to 32px tall, in a single color,
with the company name in the alt text.
If some text must move, stop it under prefers-reduced-motion: reduce and with
animation-play-state: paused on hover and keyboard focus.
Show only real customer logos; if there are none, delete the section.After the change, measure the site again with the Slop Score: the signal should be gone. To see which other signals give a generated site away, read the guide to slop patterns.
Sources
- Understanding Success Criterion 2.2.2: Pause, Stop, Hide, w3.org, November 16, 2026
- prefers-reduced-motion, developer.mozilla.org, November 16, 2026
- <marquee>: the Marquee element, developer.mozilla.org, November 16, 2026
Frequently asked questions
Is a moving logo strip bad?
It isn't a technical error, but under WCAG 2.2.2 movement that starts by itself and lasts more than five seconds needs a way to pause it. A still row usually reads better.
How do I stop an infinite CSS animation?
With animation-play-state: paused on hover or focus, and with @media (prefers-reduced-motion: reduce) { animation: none } for people who asked for less motion.