Please do not use auto-scrolling content on the web and in applications

Auto‑scroll is making phones scream — and users rage

TLDR: An audit showed auto‑scrolling makes Android’s TalkBack screen reader spew constant beeps, while iPhone’s VoiceOver stays quiet. Comments split between “follow accessibility rules and add a pause button” and “blame ad tech for hijacking scroll,” with jokes about phones sounding like arcade machines—because for many users, it’s unusable.

The internet has one request today: please stop auto‑scrolling. After an accessibility audit found Android’s TalkBack screen reader turns auto‑scrolling feeds into a nonstop “tick-tick-tick” soundtrack—like your phone’s trapped in a retro arcade—the community went full caps-lock. The author says drop auto‑scroll entirely or at least add a pause/stop. iPhone’s VoiceOver? Fine. Android’s TalkBack? Chaos. Cue the OS snark.

The comments split fast. One camp brought the hammer: professionals must follow WCAG (Web Content Accessibility Guidelines) or get out of the way. “Inexcusable,” they say—auto‑moving stuff makes some people dizzy, distracted, or totally locked out. The other camp? Blame ads. Designers aren’t the villains, says a popular take; it’s the ad scripts and growth hacks hijacking your scroll and wrecking the vibe. “Sabotage!” someone cried, picturing marketers strangling pages with code.

Jokes flew fast: “I’ve got marquee PTSD,” “my phone’s possessed by a Tamagotchi,” and “welcome to ticker‑hell.” A few folks explained the noise: those “earcons” (little sound cues) are supposed to help blind users gauge progress—until auto‑scroll hammers them like a stuck doorbell. Meanwhile, Android vs. iOS banter flared as people asked Google to fix TalkBack while others yelled: just add a pause button. For once, everyone agrees on one thing: let us stop the scroll. More on TalkBack here: link.

Key Points

  • Auto-scrolling content can create significant accessibility problems, particularly for users of screen readers.
  • In Android TalkBack (versions 16.2 and 15), auto-scrolling triggers continuous earcon sounds, making content hard to use.
  • The issue occurs in both native Android apps and on websites when using JavaScript to manipulate scrollLeft.
  • iPhone tests (iOS 26.2 and iOS 18.7.3) found VoiceOver does not exhibit the same auto-scrolling audio issue.
  • The article recommends removing auto-scrolling or at least providing controls to pause or stop moving content.

Hottest takes

it is inexcusable for any professional web developer / designer to have not read and taken to heart the WCAG — UqWBcuFx6NV4r
Adding JavaScript hooks that block the page was sabotage — hyperhello
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.