Accessibility assurance
Open-source interaction-design intelligence for AI coding agents - securely discover, select, adapt and validate UI motion, effects and interaction patterns.
npx -y skills add Suraj787/motif --skill accessibility-assuranceAssembled 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.
What its author says it does
Copied from the file, not written here
Use when an interface needs accessibility validation, keyboard operability, focus visibility, semantics, contrast, and reduced-motion, beyond automated checks alone.
SKILL.md
1.1 KB, as published. Nobody here has run it
Accessibility Assurance
Responsibility: Verify the interface is operable and perceivable for all users, and state the limits of what was actually checked.
When to invoke
- Step 16 of the root workflow, on every interface that ships.
Inputs
- The compiled implementation plan or built UI; the required-states set; motion choices.
Outputs
- A keyboard, focus, semantics, and contrast report.
- Confirmation that meaning is never carried by motion or colour alone.
- Confirmation that a reduced-motion path exists wherever motion exists.
- A clear statement of which checks were automated vs. manually verified.
Engine data + CLI
- Reads
assurance/accessibility rules andinteraction-intelligence/states. ii assure --a11y.
Notes
Never treat automated accessibility checks as complete proof. Never remove visible focus; never make essential actions hover-only. Report residual risk honestly.