Keep motion and controls accessible
Check reduced motion, keyboard use and content visibility after integration.
Motion supports the action
Off or a duration of zero removes animation without removing content or disabling the action. Supported kits also respond to the system reduced-motion preference. Keep those checks when adapting the code.
Do not add a hidden starting state to content that should remain readable without animation. Do not delay a click handler or a result message until a visual effect finishes.
Use the keyboard
Use Tab to reach controls, then the keys described in the item guide. Buttons, links and tabs have different native behavior. Keep the visible keyboard focus and the component’s local input-modality handling; do not call blur() to hide focus.
Check that hidden content cannot receive focus and that changing an example does not remove a focused control unexpectedly.
Check the whole page
Test reduced motion before loading and while the page is open. Check 200% zoom, narrow screens, forced colors, long translations and multiple component instances. A local automated test does not replace checking your integrated page or using a screen reader.