# Accessible Pagination: Page Links Everyone Can Use

Source: https://allyway.ai/glossary/accessible-pagination

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.

Accessible pagination is the row of page numbers under a blog archive, search results or a product list, built so that everyone can tell where each link leads. A sighted visitor sees "‹ 1 2 3 ›" and understands it. A screen reader user who pulls up the list of links hears "1, 2, 3, link, link" – unless the page navigation has proper names, a marked current page and a label of its own.

## What it means

[WCAG 2.4.4 Link Purpose (In Context)](https://www.w3.org/WAI/WCAG22/Understanding/link-purpose-in-context.html) (Level A) says: "The purpose of each link can be determined from the link text alone or from the link text together with its programmatically determined link context." A bare "2" or an arrow icon rarely tells you that much on its own. The fixes come straight from W3C's sufficient techniques:

| Problem | Fix | W3C technique |
|---|---|---|
| Numbers or arrows only | `aria-label="Page 2"`, "Next page" | ARIA8 – aria-label for link purpose |
| Arrow is an icon with no text | Hidden text or `aria-label` on the link | C7, ARIA8 |
| Current page not identifiable | `aria-current="page"` on its link | ARIA26 |
| Context only visual | Put the links in a list inside a labeled `nav` | H77 – link text with its list item |

The `aria-label` replaces the link text for screen readers, so it should start with the visible number ("Page 2"), which also keeps voice control working – see [label in name](https://allyway.ai/glossary/label-in-name). Every page link is a small target: give each one at least 24 by 24 CSS pixels or enough spacing to meet [target size](https://allyway.ai/glossary/target-size) (2.5.8, Level AA).

> **Note:** > **Ellipses are not links**
> The "…" between page 3 and page 12 is decoration. Keep it as plain text, not a link, and hide it with `aria-hidden="true"` if it is just a separator.

## Examples

```html title="Example"
<nav aria-label="Pagination">
  <ul>
    <li><a href="?page=1" aria-label="Previous page">‹</a></li>
    <li><a href="?page=1" aria-label="Page 1">1</a></li>
    <li><a href="?page=2" aria-label="Page 2" aria-current="page">2</a></li>
    <li><a href="?page=3" aria-label="Page 3">3</a></li>
    <li><span aria-hidden="true">…</span></li>
    <li><a href="?page=12" aria-label="Page 12">12</a></li>
    <li><a href="?page=3" aria-label="Next page">›</a></li>
  </ul>
</nav>
```

The labeled `<nav>` becomes one of the page's [ARIA landmarks](https://allyway.ai/glossary/aria-landmarks), so screen reader users can jump straight to it. Each link gets an [accessible name](https://allyway.ai/glossary/accessible-name) that says which page it opens, and `aria-current="page"` announces page 2 as the current one. Keep the current page's look distinct with more than color alone.

**Do:** Do

Use real links with `href` so every page has its own URL, label the `nav`, give number and arrow links names like "Page 3" and "Next page", mark the current page with `aria-current`, and move focus to the top of the new results after loading.

**Don't:** Don't

Build page numbers from `div` elements with click handlers, leave arrow icons without a name, show the current page by color alone, turn the "…" into a link, or reload results without telling screen reader users anything changed.

## How to check accessible pagination



## Questions

Q: Is a link that only says "2" a WCAG failure?
A: It can be. WCAG 2.4.4 lets surrounding context count only if it is programmatically determined, for example the enclosing list item or sentence. A lone number in a row of numbers usually isn't enough, so give it a name like "Page 2" with `aria-label` or hidden text.

Q: How do I mark the current page in pagination?
A: Add `aria-current="page"` to the link of the current page (W3C technique ARIA26). Screen readers then announce it as the current page. Keep a visible difference too, such as a border or bold text, not only a color.

Q: Should the arrows say "Previous" and "Next"?
A: Yes – icon-only arrows need a name. "Previous page" and "Next page" are clearer than "Previous" and "Next" when the list of links is read out of context.

Q: Is "Load more" better than pagination for accessibility?
A: Neither is better by default. A "Load more" button must be a real button, report how many new items appeared and keep focus in a sensible place. Numbered pages give each result page its own URL, which helps people return to where they were.

Q: Which WCAG criteria apply to pagination?
A: Mainly 2.4.4 Link Purpose, 2.1.1 Keyboard, 4.1.2 for the names and 2.5.8 Target Size. All are part of [WCAG 2.2](https://allyway.ai/regulations/wcag-2-2) Level AA.
