carousel-accessibility
/carousel-accessibility
Use when reviewing templates, rendered HTML, or shared components related to Make carousels accessible. Validate the final browser-facing markup, not just the source framework abstraction.
- Author
- thedaviddias ↗
- Repository
- front-end-checklist ↗
- Licence
- MIT
- Last repository change
- 06.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 2
No signals detected. Repository changed on 06.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Use when reviewing templates, rendered HTML, or shared components related to Make carousels accessible. Validate the final browser-facing markup, not just the source framework abstraction.
Original author description
Use when reviewing templates, rendered HTML, or shared components related to Make carousels accessible. Validate the final browser-facing markup, not just the source framework abstraction.
How it works
- Quick Reference
- Check
- Fix
- Explain
- Code Review
SKILL.md preview
--- name: carousel-accessibility description: "Use when reviewing templates, rendered HTML, or shared components related to Make carousels accessible. Validate the final browser-facing markup, not just the source framework abstraction." metadata: category: html priority: medium difficulty: advanced estimatedTime: "30" source: frontendchecklist.io url: https://frontendchecklist.io/rules/html/carousel-accessibility --- # Make carousels accessible Auto-playing carousels without controls trap users, cause disorientation, and violate WCAG requirements—proper implementation ensures all users can interact with slideshow content. ## Quick Reference - Always provide pause/stop controls for auto-rotating carousels - Support keyboard navigation with arrow keys and tab - Use aria-live regions to announce slide changes - Respect prefers-reduced-motion preference ## Check Verify carousels have pause/play controls, keyboard navigation, proper ARIA roles, and respect prefers-reduced-motion. ## Fix Implement carousels with pause buttons, arrow key navigation, aria-live for announcements, and motion preference support. ## Explain Explain accessibility requirements for carousels including auto-play controls, keyboard access, and screen reader support. ## Code Review Review templates, server-rendered HTML, and shared components that output markup related to Make carousels 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/rules/html/carousel-accessibility
Files in this package (2)
- SKILL.md 2 KB
- references/rule.md 10 KB
Versions
The database has no other skills named carousel-accessibility.
Database snapshot: 13.11.2026 · package version 74e35dd260a7 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100draggable-accessibility
Use when reviewing templates, rendered HTML, or shared components related to Make drag and drop accessible. Validate the final browser-facing markup, not just the source framework abstraction. - 100video-accessibility
Use when reviewing templates, rendered HTML, or shared components related to Make videos accessible with captions. Validate the final browser-facing markup, not just the source framework abstraction. - 100html-syntax-and-semantics
Rules for writing valid, semantic, accessible HTML. Use when writing or reviewing any HTML, JSX markup, templates or email-less web pages, including document structure, element choice, forms, images, links, tables and accessibility basics. - 100wp-accessibility-review
WordPress accessibility review for themes, blocks, plugins, and admin interfaces. Use when reviewing keyboard navigation, focus behavior, semantic HTML, ARIA usage, form labeling, screen-reader support, contrast-related implementation issues, or when user mentions "accessibility… - 100ensuring-accessibility
WCAG 2.1 AA implementation patterns for building accessible frontend components: semantic HTML first, keyboard navigation and focus management, ARIA only where HTML falls short, contrast minimums, and an axe-core verification step. Use when implementing accessible components,… - 85html-semantic-recipes
Provides semantic HTML5 markup patterns for common UI components (breadcrumbs, cards, navigation, forms, login, accordion, definition lists, checkbox groups) adapted for HTML, React, Vue, Angular, Svelte, and Astro. Use when writing or generating UI markup, building accessible…