The guideline
Avoid pure infinite scroll — content injected automatically as the user nears the bottom, with no explicit action to request it — for any list a user needs to finish, compare, or exit from cleanly. Use numbered pagination, or an explicit "Load More" button the user triggers directly, instead. If infinite loading is used regardless, implement the ARIA feed pattern (role="feed" with an accessible name and boundary on each loaded article) so screen readers can enter, read and deliberately advance the region rather than colliding with an unannounced stream, and keep a route past it to the footer and global navigation that does not depend on scrolling through everything that has loaded. Whichever mechanism is used, its trigger — a page link or the Load More button — must be a visible, keyboard-reachable, adequately sized control, not only a scroll-position listener with no static affordance.
Common failures
- The site uses infinite scrolling to load products continuously without pagination or manual load controls, making it difficult for users to return to previously viewed items or reach the footer, and degrading browser performance on longer sessions.
Where it applies
Pages
Disciplines
Devices
Why it matters, how to fix it, and the research behind it
Rubric's full guide adds the reasoning, the fix and the sources for this check, and checks your client's pages against it and hundreds of others. Findings come back worst first.