# Infinite Scroll: Keyboard and Screen Reader Access

Source: https://allyway.ai/glossary/infinite-scroll

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](https://allyway.ai/glossary/keyboard-navigation). See the W3C [Understanding page for 2.1.1](https://www.w3.org/WAI/WCAG22/Understanding/keyboard.html).

Several other [WCAG 2.2](https://allyway.ai/regulations/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](https://allyway.ai/glossary/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](https://allyway.ai/glossary/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](https://www.w3.org/WAI/ARIA/apg/patterns/feed/): 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.

> **Tip:** > **A "Load more" button solves most problems**
> Instead of loading on scroll, show the first batch with a button below it. Keyboard users decide when to load, the footer stays reachable, and focus can move to the first new item. A classic [accessible pagination](https://allyway.ai/glossary/accessible-pagination) also works, especially for search results people want to share or come back to.

## Examples

```html title="Example"
<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>
```

**Do:** Do

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.

**Don't:** Don't

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

Q: Is infinite scroll bad for accessibility?
A: 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.

Q: Does WCAG forbid infinite scroll?
A: 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).

Q: What is better for accessibility: infinite scroll or pagination?
A: 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.

Q: How do I make the footer reachable with infinite scroll?
A: 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.

Q: How can I test my site's keyboard access quickly?
A: Use Tab, Shift+Tab and Enter through your page with the mouse aside. The free [WCAG scanner](https://allyway.ai/free-wcag-accessibility-scanner-for-websites) adds an automated check of common issues on your homepage.
