UI Accessibility Motion

Make the UI semantically correct and operable before polishing visual motion.

Process

Prefer semantic HTML over ARIA; do not use ARIA to repair bad structure.
Use buttons for actions and links for navigation.
Ensure every form control has a label and field errors are associated with the control.
Verify keyboard navigation, focus order, visible focus, modal focus trap, Escape behavior, Enter/Space activation and post-action focus.
Use ARIA only when native semantics are insufficient; avoid hiding focusable elements with aria-hidden.
Do not communicate meaning only through color, hover, animation, icon or tooltip.
Respect reduced motion and provide low-motion alternatives for large movement, parallax, zoom and long transitions.
Use animation only when it explains state, relationship, progress or feedback; avoid animation that blocks work, hides slow APIs or causes reflow.