Reduced Motion Support
Respect people who asked their device for less animation.
What it adds
An app-wide motion setting driven by the system preference, with an in-app override and legible non-animated alternatives.
What your agent is told to do
6
What your agent is told to do
6-
1
Audit every animation in the app — transitions, parallax, auto-advancing carousels, looping loaders, shimmer, confetti, scroll effects, chart entry animations — and list which are decorative and which carry meaning.
-
2
Route all motion through one place, so the preference is applied once rather than remembered per component.
-
3
Default to the operating system's prefers-reduced-motion setting and let the user override it in settings, because the OS setting is often wrong for a shared or managed machine. Persist the override.
-
4
Replace removed motion with something that still communicates the change: an instant state swap plus a colour or position change, a short cross-fade, or a message. The point is less motion, not less feedback.
-
5
Apply the preference to third-party components, charts, embedded video, and animated images by disabling their animation options where the library exposes one.
-
6
Do NOT simply set all animation durations to zero globally. Elements will teleport, panels will appear with no indication of where they came from, and the result disorients the same users the setting was meant to help.
Edge cases it handles
7
Edge cases it handles
7- Reduced motion does not mean no opacity change — small cross-fades are generally safe and preserve continuity.
- Autoplaying and looping media must not start under reduced motion, and needs a visible play control instead.
- Loading indicators that rely on spin need a static or text alternative, or the user loses all sense of progress.
- The preference can change while the app is open; listen for the change rather than reading it once at boot.
- Scroll-triggered reveals must leave content visible when motion is off, not permanently hidden at zero opacity.
- Toasts and drawers that slide in should still appear and disappear distinctly enough to be noticed without the slide.
- Test with the setting on. Most reduced-motion bugs are elements that simply never become visible.
Definition of done
9
Definition of done
9- Every animation in the app is covered by the motion setting.
- The setting defaults to prefers-reduced-motion and can be overridden in-app, with the choice persisted.
- A change in the system preference is picked up without a reload.
- Removed animations are replaced by a legible alternative, not by an abrupt jump.
- No content is left invisible or unreachable when motion is disabled.
- Autoplaying and looping media do not start under reduced motion.
- Third-party components and charts honour the setting where they allow it.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Focus Ring System
Focus Ring System
Give every focusable control one clear focus indicator that belongs to the design.
What it does
A single focus treatment applied consistently across buttons, links, inputs, cards, rows, and custom controls.
How it works
- 1 Inventory every focusable element in the app, including the ones made focusable by hand — clickable rows, cards, canvas objects, custom selects — and confirm each shows the shared treatment.
- 2 Distinguish focus arriving from the keyboard from focus arriving from a click, and show the ring for keyboard and programmatic focus. A ring appearing on every mouse press reads as a rendering fault and invites someone to remove it entirely.
- 3 Compose the ring so it stays visible on every surface the control can sit on: page background, card, coloured button, dark toolbar, selected row. A single-colour ring will disappear against at least one of them.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/focus-ring-system
Auto Captions
Auto Captions
Every uploaded video gets timed captions without anyone typing them out.
What it does
An automatic captioning pass over uploaded video that produces a timed caption track shown in the player.
How it works
- 1 Extend the app's existing Voice Transcription rather than adding a second speech pipeline. What is new here is timing, storage as a caption track, and player integration, not the recognition itself.
- 2 Run captioning as a background job triggered after the upload finishes, and reuse the app's existing job progress reporting so the user can see where a long file has got to.
- 3 Store the caption track as its own record linked to the media, with a language, a status, and a source marking it as machine-generated so a human correction can supersede it later.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/auto-captions
Accessible Name Validator
Accessible Name Validator
Find every control a screen reader announces as nothing useful.
What it does
An audit of the computed accessible name of each interactive element in the rendered interface.
How it works
- 1 Compute the name the way assistive technology does — following the resolution order through labels, referenced elements, attributes, and text content — rather than reading the source markup and guessing.
- 2 Report three separate failures: an empty name, a generic name such as button, link, or here, and duplicate names within the same context where several controls announce identically.
- 3 Prefer a fix that adds a visible label. A control given a hidden name is announced but still mysterious to the sighted user who cannot tell two identical icons apart.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/accessible-name-validator
How it works
-
1
Copy the link
Grab the Markdown instruction URL for this feature.
-
2
Give it to your AI
Paste it into Claude Code, Cursor, v0, Lovable — whatever you build with.
-
3
It inspects, then implements
Your agent reads your existing app first, then adds the feature to fit it.
Works with your stack
These instructions are written to adapt. They tell the agent to detect your framework, match your existing design system, and reuse what you already have — rather than assuming a particular stack.
Need it tighter than that? Customize the feature and tell it exactly what you're running.