Sequencing a page against the reader’s own movement
Choreography means treating position in a document as a timeline: revealing an argument in the order it should land, holding a subject still while explanation moves past it, changing a background as the topic changes. Done well, a reader barely registers the technique and simply finds the page easy to follow.
Why most scroll work fails
Three failures account for nearly everything that goes wrong, and all three are avoidable.
Hijacking
A page that overrides normal scrolling to enforce its own pacing has taken away the one control the visitor had. Somebody scanning for a fact now cannot reach it, and momentum scrolling on a trackpad fights the script continuously. The technique reads as a designer prioritizing their sequence over the reader’s intent.
Content locked behind animation
When text only exists after an element has animated into view, anyone who scrolls quickly passes emptiness, and anyone whose script failed sees nothing at all. A search crawler frequently sees nothing either.
Effects with no relationship to meaning
Elements sliding in from alternating sides, applied uniformly to every section, because the library made it easy. The movement communicates nothing, so it becomes noise the reader learns to ignore.
The rules we build to
Content exists first, and animation adjusts what is already present rather than delivering it. A page with every script disabled must still read completely, which is also the condition that makes it legible to a crawler. Scroll position is never taken from the visitor. Movement is linked to where they have chosen to be, so a reader who scans quickly gets the whole page quickly, while a reader who moves slowly sees the sequence unfold.
Effects earn their place individually. A subject held in place while explanation moves past it is doing genuine work. A section that fades in because the preset offered it is not, and we cut it. Anything triggered on entry uses the browser’s own visibility observation rather than continuous position calculation, since work performed on every scroll event is the standard cause of stutter.
Reduced motion, handled properly
A visitor who has requested reduced motion at the system level needs the page to work without the choreography, and that reading has to be designed rather than derived by switching effects off. Content that would have revealed on scroll is simply present. Movement across large distances is replaced by a change in opacity or removed. Anything held in place releases. Continuous motion stops.
"The test is that somebody using the reduced version should not be able to tell that something was removed. If the page feels incomplete, the animation was carrying meaning that should have been in the content."
What works on a phone
Most scroll technique is designed on a large screen and degrades badly on a small one, where the viewport is short, the connection is variable and the hardware is slower. Sequences that depend on a wide canvas have no room, elements pinned in place can consume the entire screen, and effects tuned to a long desktop scroll fire in rapid succession over a short mobile one. So the mobile reading is designed separately rather than inherited, and it is usually simpler by decision rather than by compromise.
Performance rules
Choreography is the easiest place on a page to cause stutter, because the work happens continuously during an interaction the visitor can feel. Only properties the browser can hand to the graphics card are animated, which in practice means transforms and opacity. Layout properties are avoided, since animating them forces recalculation every frame. Observation is used in place of scroll listeners. Calculations are cached rather than recomputed. Anything outside the viewport stops entirely.
Where scroll work connects
The interaction principles behind smaller movement are covered in motion design, rendered visuals that sit behind a scrolling page are covered in interactive experiences, and the behavior of layouts across viewport sizes is covered in responsive layouts.
How the engagement runs
Choreography is built and reviewed through screen shared sessions on real devices, because the difference between smooth and slightly wrong is only detectable in use. If a previous build gave you scroll effects that felt impressive in review and irritating in use, the cause was almost certainly hijacking, content locked behind animation, or effects with no relationship to meaning.