November 14, 2026

Scroll-Jacking: When Forced Scrolling Should Go

If a page changes the speed or direction of scrolling, take that control back. Check the same journey on a phone, and ask for the content without the forced movement.

A black knurled scroll wheel in an aluminum cradle on a pink background, locked by a chrome C-clamp with a blue handle, above a white arrow pointing sideways.
In this guide

A shopper on the fictional Harbor & Pine site is trying to move down a collection page. Instead of moving down the page, scrolling sends the shopper through a sideways tour of sofas. When they try to go back, the page snaps to the next staged view. The path they wanted, past the seating and down to the delivery details, is no longer theirs to follow.

If a page changes the speed or direction of scrolling, ask what that behavior helps the visitor understand. If it blocks the route to information such as delivery details, ask the team to restore normal scrolling.

The Harbor & Pine example is fictional, not a test result.

Separate Animated Content From Altered Scrolling

Nielsen Norman Group defines scroll-jacking, or scroll hijacking, as a design pattern that changes the speed and, sometimes, the direction of scrolling on a web page.

That is different from an animation that plays as you scroll, while the page still follows your movement. If content fades or slides in and you can still scroll, stop, and go back at a normal pace, start with When Does Scroll-Driven Animation Help?. If a background layer moves at a different speed but the scroll itself is unchanged, use Parallax and Background Motion.

Use this recognition check first:

  • If the content moves and scrolling still feels like scrolling, this is not scroll-jacking.
  • If the page redirects, slows, or reshapes the scrolling action, it is.

Why Forced Scrolling Deserves Challenge

In a 2023 usability study of sites from several industries, all using some form of scroll-jacking, Nielsen Norman Group found that the majority of participants were at least mildly disoriented. Everyone who visited one fully scroll-jacked page was disoriented. Some people scrolled up and down rapidly to get their bearings, or thought their usual way of scrolling had failed.

The same study found that scroll-jacks were tolerated best when they were used to reveal relevant information a little at a time. Even then, a couple of people took the last image as the end of the page. Effects that ran too fast meant people missed content. Effects that ran too slowly caused scroll fatigue.

They report that most of the problems seen on desktop were worse on mobile, where scroll-jacks can last longer and disorient more, and they advise avoiding scroll-jacking on mobile because in most cases the benefits are not worth the extra work. Their other advice is to avoid changing scroll direction, limit the text in a scroll-jacked section, include ordinary scrolling sections, test the scroll rate, and use a scroll-jack only for critical information. Their overall finding is that scroll-jacking leads to more user pain than benefits.

Leave the choice to the visitor. A page can still tell a story in a room, or reveal a sequence, without taking the wheel.

Review the Same Journey on a Real Phone

Paste the page address into Online Website Previewer and press Preview. Start at 1920 by 1080 CSS pixels, then compare 390 by 844 and 820 by 1180, the tool’s phone and tablet sizes. You can scroll the live page and notice whether the movement follows you. The preview does not copy touch input, so open the same address on a real phone and repeat the same route. Phone Preview vs Real Phone: What to Check explains that limit.

These are reviewer questions, not a published test script:

  • Does the page follow at the pace you expect, or does it run ahead or drag?
  • Can you go back up without being snapped to the next scene?
  • Can you reach the footer and the information you came for, such as delivery details on the Harbor & Pine page?
  • When you scroll with a keyboard, can you reach the delivery details and return to the previous section? Describe any unexpected movement and ask the team to investigate. This is your own check, not a sourced method.

WCAG 2.2 Success Criterion 2.3.3 is Level AAA, a target. It treats visitor-controlled scrolling as essential and asks that non-essential motion added to scrolling be controllable. The criterion does not name scroll-jacking. Treating a hijacked scroll as a problem under that criterion is our reading, not a ban in the standard. Do not write a compliance verdict. Ask the team to show the same content without forcing the movement.

A useful note might say: “On the Harbor & Pine seating collection at [address], on a real phone, vertical scrolling turns into a sideways room tour and I cannot stop on the delivery section or go back smoothly. In the 1920 by 1080 preview the same sideways takeover was visible. Please let the page scroll normally, and keep the room sequence as content the visitor can move through at their own pace.”