A capability stays maintainable only when the team can explain every state, retry, and piece of residual data—not merely show one successful run. A clickable div drop zone is inaccessible. Use native file input plus label, keep drag-and-drop as enhancement, and expose every action as a focusable control.
Accessibility is not a late set of ARIA attributes. Keyboard, screen-reader, zoom, reduced-motion, and high-contrast users need the same complete task and a discoverable next step after errors.
Questions the design must answer
List non-negotiable invariants before selecting performance knobs. Tuning can roll out gradually; identity, permission, and terminal-state rules cannot drift at runtime.
- Use real buttons with descriptions, do not steal focus for new tasks, restore focus after cancel, and avoid overriding system shortcuts.
- Separate protocol facts, user intent, and automatic recovery; automation may restore facts but never overturn an explicit choice.
- Ship conservative defaults, server-side ceilings, and a rollout switch instead of trusting browser-provided numbers as resource budgets.
The delivery standard for Completing File Transfer with a Keyboard from Selection to Cancel is a usable normal path, convergent failures, bounded resources, and a state users can understand. The result is a production capability that can be explained, degraded safely, and rolled back—not a demo that works once.
Edge cases are part of the feature
Failure and success must share one state model. An error toast that neither releases resources nor propagates a terminal state leaves dirty work for the next recovery attempt.
- A display:none file input can disappear from assistive tech, while rebuilding the list drops focus to body.
- Fixing only the UI leaves queues, locks, or expired credentials for the next operation to inherit and fail again.
- Ideal-size tests miss large files, long sessions, and concurrency that cross hidden limits and cause cascading failure.
Prove that it works with evidence
Do not stop verification when the final action succeeds. Count side effects, measure wait time, inspect privacy, and prove the next run begins from a clean baseline.
- Without a mouse, complete single/multiple file, reject, pause, cancel, and retry while focus and announced context survive list changes.
- Race refresh, cancel, timeout, and remote completion in one scheduling window; assert one terminal state and one side effect.
- Before release, record success rate, p50/p95/p99 latency, error classes, and resource high-water marks with explicit rollback thresholds.
A capability becomes maintainable when it degrades safely, repetition adds no side effects, and its signals reveal a fault before user reports do.