Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Use when reviewing templates, rendered HTML, or shared components related to Make pagination accessible. Validate the final browser-facing markup, not just the source framework abstraction.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-16 | ✗→✓ | ▲ Improved | -3% | 0% |
| case-22 | ✗→✓ | ▲ Improved | -16% | 0% |
| case-01 | ✓→✓ | = Same ✓ | -16% | 0% |
| case-02 | ✓→✓ | = Same ✓ | -24% | 0% |
| case-03 | ✓→✓ | = Same ✓ | -4% | 0% |
Without proper markup, screen reader users cannot understand which page they're on or navigate efficiently through paginated content.
Verify pagination uses nav element with aria-label, indicates current page with aria-current, and is keyboard navigable.
Implement pagination with nav role='navigation', aria-label, aria-current='page' for active page, and focusable controls.
Explain how accessible pagination helps screen reader users understand their position and navigate through paged content.
Review templates, server-rendered HTML, and shared components that output markup related to Make pagination accessible. Flag exact elements, attributes, and routes where the rendered HTML violates the rule.
For full implementation details, code examples, and framework-specific guidance, see references/rule.md.
Rule page: https://frontendchecklist.io/en/rules/html/pagination-accessibility
Other measured skills in the registry, with their headline benchmark lift.