A row of page numbers can look familiar while leaving visitors uncertain about where they are. If the current page differs only by a faint colour, the control asks users to infer state from a subtle decoration. Pagination should communicate that state directly.
The MDN documentation for aria-current describes marking the current item in a set. In a page-navigation control, aria-current=”page” can identify the current page for assistive technology. The attribute supplements sensible markup and visible design; it does not create the navigation by itself.
Make the control understandable in context
Use a navigation region with an appropriate label, especially if the page contains several navigation areas. Make page destinations actual links when they navigate to URLs. Give the current page a clear visible treatment that does not depend solely on colour.
Consider what “Previous” and “Next” mean at the boundaries. On the first page there is no previous results page; an apparently active control that does nothing is confusing. Choose a clear, consistent boundary treatment rather than a broken link.
Test the journey through results
- Navigate using the keyboard and check visible focus.
- Confirm that only the intended page is marked current.
- Check that filters and sorting remain consistent.
- Use browser back and forward after changing pages.
- Test a narrow screen without hiding essential controls.
If results update dynamically, manage the changed content and focus deliberately so users can understand what happened. Do not assume a new set of cards appearing visually is sufficient feedback for every visitor.
A helpful pagination control answers two questions quickly: where am I, and where can I go next? Styling, semantics and navigation behaviour should all support those answers.

