Accessible Focus Management
Put keyboard and screen-reader users in the right place after the interface changes.
What it adds
A deliberate policy for where focus goes whenever the page changes underneath the user — navigation, validation, deletion, insertion, and async updates.
What your agent is told to do
6
What your agent is told to do
6-
1
Inventory every moment the interface changes without a full page load: client-side route changes, form submissions, rows being deleted, content being appended, filters re-rendering a list.
-
2
Decide for each one whether focus should move, and write it down. On a route change, move focus to the new page heading or main region so a screen reader starts reading the new page instead of staying on a link that no longer exists.
-
3
When validation fails, move focus to the first invalid field and make sure its error message is associated with it, so the user hears the problem rather than hunting for it.
-
4
When an element that had focus is removed, move focus to a stable neighbour — the next row, the list container, or the control that triggered the removal. Never let focus fall back to the document body; the user loses their position entirely.
-
5
Announce background changes (saved, imported, ten new results) through a polite live region, and route all such announcements through one shared mechanism rather than scattering live regions through the markup.
-
6
Do NOT move focus for updates the user did not initiate — a poll result, an incoming notification, an autosave. Stealing focus mid-sentence destroys typed input and is far worse than silence.
Edge cases it handles
7
Edge cases it handles
7- Focus must never be sent to an element that is hidden, disabled, or already detached from the document.
- An element that only exists to receive focus needs tabindex="-1", not tabindex="0" — it should be programmatically focusable but stay out of the tab order.
- Focus moves must happen after the new content is actually in the DOM, not in the same tick as the state change.
- An assertive live region interrupts whatever is being read; reserve it for errors and use polite everywhere else.
- Rapid successive updates must be coalesced before announcing, or the user hears a stream of half-read messages.
- Deleting the last row of a list leaves nothing to focus — send focus to the empty state and make sure the empty state is focusable.
- Scrolling caused by a focus move must not jump the viewport unexpectedly; keep the target in view without an animated scroll when prefers-reduced-motion is set.
Definition of done
8
Definition of done
8- Every interface change that removes or replaces the focused element has a defined focus destination.
- A client-side route change moves focus into the new page content.
- A failed validation moves focus to the first invalid field with its error associated.
- Deleting an item leaves focus on a sensible neighbour, never on the body.
- Background updates are announced through a shared polite live region and never steal focus.
- Focus is never moved to a hidden, disabled, or removed element.
- 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
Touch Target Checker
Touch Target Checker
Find the controls that are too small or too crowded to hit reliably on a phone.
What it does
A development-time audit reporting the measured hit area and neighbour spacing of every interactive element.
How it works
- 1 Measure the element's actual activation area — the region that responds to a tap — rather than the icon or glyph drawn inside it, since padding and pseudo-element extensions frequently make a small icon a perfectly adequate target.
- 2 Check the gap between adjacent targets as well as their size. Two comfortable buttons sitting flush against each other still produce mis-taps, and the report must say which of the two problems it found.
- 3 Report the offending elements with enough context to locate them — the route, the component, and a way to highlight the element on the page — rather than a count of failures.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/touch-target-checker
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.