drag-drop-pointer-accessibility-audit

Inventory every dragging interaction, then verify a non-dragging single-pointer alternative per WCAG 2.5.7 and a complete keyboard path. Test the full lifecycle including instructions, cancellation, reorder feedback, focus behavior, and error recovery, and record evidence for each finding.

For each multipoint or path-based gesture like swipe or pinch, check that a simple single-pointer alternative achieves the same outcome, as required by WCAG 2.5.1. Keyboard access alone does not satisfy this criterion, so test the actual single-pointer path on real or emulated touch environments.

No. WCAG 2.5.1 and 2.5.7 require a simple single-pointer alternative, and keyboard access cannot substitute for it. Keyboard operability remains a separate requirement under 2.1.1 and should be tested independently.

WCAG 2.5.8 requires a minimum of 24 by 24 CSS pixels at Level AA, subject to spacing, inline, equivalent-control, and essential exceptions. The 44 by 44 pixel size in 2.5.5 applies only at Level AAA or as an advisory goal.

Only partially. Source review can confirm deterministic code defects, but target geometry, gesture recognition, focus movement, computed accessible names, and announcements require runtime or assistive-technology testing and should be marked needs-validation otherwise.

Avoid it for full legal conformance audits, pure keyboard or focus reviews without pointer interactions, and general contrast or responsive-layout questions. It also does not implement fixes; it only reviews and reports findings.