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 drag and drop accessible. Validate the final browser-facing markup, not just the source framework abstraction.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-06 | ✗→✓ | ▲ Improved | -28% | 0% |
| case-10 | ✗→✓ | ▲ Improved | 11% | 0% |
| case-04 | ✓→✓ | = Same ✓ | -24% | 0% |
| case-13 | ✓→✓ | = Same ✓ | 5% | 0% |
| case-05 | ✓→✓ | = Same ✓ | -24% | 0% |
Drag and drop is mouse-dependent by default—keyboard and screen reader users are completely locked out without proper alternatives and ARIA announcements.
Verify drag and drop interfaces have keyboard alternatives, proper ARIA attributes, and live region announcements.
Implement keyboard alternatives (arrow keys, Enter/Space), aria-grabbed, aria-dropeffect, and status announcements.
Explain how accessible drag and drop implementations provide equivalent functionality for keyboard and screen reader users.
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/en/rules/html/draggable-accessibility
Other measured skills in the registry, with their headline benchmark lift.