CtrlK
BlogDocsLog inGet started
Tessl Logo

pagination-accessibility

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.

55

Quality

62%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/pagination-accessibility/SKILL.md
SKILL.md
Quality
Evals
Security

Make pagination accessible

Without proper markup, screen reader users cannot understand which page they're on or navigate efficiently through paginated content.

Quick Reference

  • Use nav element with aria-label='Pagination'
  • Mark current page with aria-current='page'
  • Provide clear labels for previous/next buttons
  • Announce page changes to screen readers

Check

Verify pagination uses nav element with aria-label, indicates current page with aria-current, and is keyboard navigable.

Fix

Implement pagination with nav role='navigation', aria-label, aria-current='page' for active page, and focusable controls.

Explain

Explain how accessible pagination helps screen reader users understand their position and navigate through paged content.

Code Review

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

Repository
thedaviddias/Front-End-Checklist
Last updated
First committed

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.