draggable-accessibility
/draggable-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.
- 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 drag and drop 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 drag and drop 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: draggable-accessibility description: "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." metadata: category: html priority: medium difficulty: advanced estimatedTime: "35" source: frontendchecklist.io url: https://frontendchecklist.io/rules/html/draggable-accessibility --- # Make drag and drop accessible Drag and drop is mouse-dependent by default—keyboard and screen reader users are completely locked out without proper alternatives and ARIA announcements. ## Quick Reference - Always provide keyboard alternatives to drag and drop - Use aria-grabbed and aria-dropeffect (or newer attributes) - Announce drag operations to screen readers via live regions - Support both mouse/touch and keyboard interaction patterns ## Check Verify drag and drop interfaces have keyboard alternatives, proper ARIA attributes, and live region announcements. ## Fix Implement keyboard alternatives (arrow keys, Enter/Space), aria-grabbed, aria-dropeffect, and status announcements. ## Explain Explain how accessible drag and drop implementations provide equivalent functionality for keyboard and screen reader users. ## Code Review Review templates, server-rendered HTML, and shared components that output markup related to Make drag and drop 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/draggable-accessibility
Files in this package (2)
- SKILL.md 2 KB
- references/rule.md 11 KB
Versions
The database has no other skills named draggable-accessibility.
Database snapshot: 13.11.2026 · package version b57f45efbdd9 (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
- 100carousel-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. - 100accessible-notifications
Use when reviewing templates, rendered HTML, or shared components related to Make notifications accessible. Validate the final browser-facing markup, not just the source framework abstraction. - 100wp-admin-drag-and-drop
Build WordPress admin drag-and-drop UI with core's bundled jQuery UI Sortable, Draggable, Droppable, optional `jquery-touch-punch`, `wp-api-fetch`, and `wp-a11y.speak()`. Covers flat reorder lists, connected lists / kanban columns, palette-to-dropzone clones, hierarchical tree… - 100officeimo-website-wasm
Use when adding or changing OfficeIMO.com browser tools (/browser/<tool>/ pages and the /convert/ directory), the browser-local OfficeIMO engine (Website/Apps/OfficeIMO.Web.Converter), its WebAssembly publishing, or static-site integration for drag/drop document tools. - 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…