Infinite Scroll: Keyboard and Screen Reader Access
Also called: Endless scrolling, Infinite scrolling, Scroll feed
Definition
Infinite scroll is a pattern that loads more items automatically when the user nears the end of a list. It is accessible when keyboard and screen reader users can load, reach and leave the content, and when content after the list stays reachable.
Infinite scroll keeps adding posts, products or search results as you move down a page, so there is no "next page" button. For mouse users that feels effortless; for keyboard and screen reader users it can turn into a trap: every time they get close to the footer, new items push it away, and the contact link or imprint at the bottom is never reached.
What it means
WCAG success criterion 2.1.1 Keyboard (Level A) says: "All functionality of the content is operable through a keyboard interface without requiring specific timings for individual keystrokes." With infinite scroll this covers more than the items themselves. Loading more content, moving between items and getting past the list to the rest of the page are all functionality, so all of them must work with the keyboard. See the W3C Understanding page for 2.1.1.
Several other WCAG 2.2 criteria come into play:
| Problem | Criterion | What to do |
|---|---|---|
| Footer or links after the list can't be reached | 2.1.1 Keyboard (A) | Offer a "Load more" button or a way to skip the feed |
| Focus jumps to the top when items load | Focus Order 2.4.3 (A) | Keep focus where it was, or on the first new item |
| Screen readers don't notice new items | Status Messages 4.1.3 (AA) | Announce "20 more products loaded" |
| Endless list with no orientation | Good practice | Tell users the position, e.g. "item 21 of 60" |
The W3C ARIA Authoring Practices describe a dedicated feed pattern: a container with role="feed" that holds article elements. Inside the feed, Page Down and Page Up move between articles, and Control + End moves focus to the first focusable element after the feed. W3C notes there is no established convention for these keys, so document them on the page.
Examples
<section aria-labelledby="news-title">
<h2 id="news-title">Latest news</h2>
<ul id="news-list">
<li><a href="/news/1">…</a></li>
<!-- 19 more items -->
</ul>
<button type="button" id="load-more">Load 20 more articles</button>
<p role="status" id="load-status"></p>
</section>
<script>
// After loading: move focus to the first new link, then announce it
firstNewLink.focus();
document.getElementById('load-status').textContent =
'20 more articles loaded, 40 of 120 shown.';
</script>Use a real <button> to load more, keep focus on or near the new content, announce new items in a status region, keep the footer reachable and give the list a heading. With role="feed", set aria-busy="true" while loading and back to false when done.
Load items on scroll with no button, move focus to the top of the page, rebuild the whole list so focus is lost, or put essential links only in a footer that new content keeps pushing away.
How to check infinite scroll
Questions
Is infinite scroll bad for accessibility?
Not by itself, but it often breaks keyboard access: links after the list can't be reached, focus jumps and new content is not announced. A "Load more" button or pagination avoids most of these problems.
Does WCAG forbid infinite scroll?
No. WCAG doesn't mention infinite scroll. What it requires is that every function works by keyboard (2.1.1), that focus moves in a logical order (2.4.3) and that status messages reach screen readers (4.1.3).
What is better for accessibility: infinite scroll or pagination?
For lists people browse with a goal, such as search results or shop categories, pagination or a "Load more" button is usually easier: the user controls loading, can reach the footer and can return to a page. Infinite scroll can work for social feeds if it follows the W3C feed pattern.
How do I make the footer reachable with infinite scroll?
Stop loading automatically and offer a "Load more" button, add a skip link past the feed, or move key footer links like contact and imprint into the header as well.
How can I test my site's keyboard access quickly?
Use Tab, Shift+Tab and Enter through your page with the mouse aside. The free WCAG scanner adds an automated check of common issues on your homepage.
Related terms
Keyboard Navigation: WCAG 2.1.1 Explained
Keyboard navigation means that every function of a website can be reached and operated with a keyboard alone – usually with Tab, Shift+Tab, Enter, Space and the arrow keys. WCAG 2.1.1 requires it at Level A.
Read definition: Keyboard Navigation: WCAG 2.1.1 ExplainedFocus Order: Logical Tab Order Explained (WCAG 2.4.3)
Focus order is the sequence in which interactive elements receive keyboard focus when a user presses Tab. WCAG 2.4.3 requires that this sequence preserves the meaning and operability of the page.
Read definition: Focus Order: Logical Tab Order Explained (WCAG 2.4.3)Status Messages: Announce Updates Without Focus
Status messages are changes in content that tell users about the result of an action, a waiting state, the progress of a process or the existence of errors, without changing the context. WCAG 4.1.3 requires that they can be programmatically determined, so assistive technologies can present them without giving them focus.
Read definition: Status Messages: Announce Updates Without FocusAccessible Pagination: Page Links Everyone Can Use
Accessible pagination is a set of page links – 1, 2, 3, Previous, Next – that screen reader and keyboard users can understand and use: the links say which page they open, the current page is marked in code, and the whole block is a labeled navigation. Unclear page links fall under WCAG 2.4.4 Link Purpose (In Context) at Level A.
Read definition: Accessible Pagination: Page Links Everyone Can Use