Motion accessibility
Use when validating that an interaction preserves keyboard access, focus, semantics, and honors reduced-motion before it can ship.From its SKILL.md
npx -y skills add Suraj787/motif --skill motion-accessibilityAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.3 KB, 241 tokens by cl100k_base, as published. Nobody here has run it
Motion Accessibility
Responsibility: Enforce the mandatory accessibility and reduced-motion invariants. This is a non-negotiable gate.
When to invoke
- During implementation and again at validation (step 12 of the root workflow).
Inputs
- The implemented interaction and its reduced-motion variant.
Outputs
- Pass/fail per invariant, with required fixes.
Invariants
- Keyboard focus is never removed or obscured; focus order stays logical.
- Essential actions are never hover-only; they work via keyboard and touch.
- Status is never conveyed by motion alone, pair with text/icon/ARIA.
prefers-reduced-motion: reduceis respected with a meaningful non-motion path.- Decorative motion never blocks or delays input.
- Semantics (roles, names, states) are correct and announced.
How it connects
- Reads
intelligence/accessibility guidance; does not touchregistry/ranking. - Reports to
implementation-validation; failures block the ship.
Notes
A reduced-motion path is not "disable the animation and leave a gap", it must still communicate the state change clearly. No interaction ships without it.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.