Accessible Name Validator
Find every control a screen reader announces as nothing useful.
What it adds
An audit of the computed accessible name of each interactive element in the rendered interface.
What your agent is told to do
5
What your agent is told to do
5-
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.
-
4
Handle icon-only buttons and composite controls explicitly: a control built from an icon, a count, and a status dot must resolve to one coherent phrase, not a run-on of three fragments.
-
5
Do not fix a missing name by stacking attributes. Overlapping naming and description attributes produce double announcements, and the validator should flag that as its own failure rather than only the absence of a name.
Edge cases it handles
7
Edge cases it handles
7- Empty names, generic names, and names duplicated across sibling controls are three distinct failures with three different fixes, and a validator reporting only emptiness misses most real cases.
- A visible label is preferable to a hidden one wherever the layout allows it, because the hidden name helps only some users and leaves the ambiguity in place for everyone else.
- Icon-only controls and composite controls need a deliberate name; letting the name fall through to the concatenated text of the children produces announcements like edit 3 overdue.
- Conflicting naming and description attributes cause the same phrase to be read twice, which the audit must catch rather than treating any non-empty name as a pass.
- Names generated from record data must be checked with real values, since a row action named after an empty or untitled record announces as nothing at all.
- In a translated interface the name must come from the same translation source as the visible text, or the two drift and the spoken label stops matching the screen.
- Controls rendered only in an open menu, dialog, or drawer must be included, which means the audit has to open them rather than scanning the initial page.
Definition of done
9
Definition of done
9- Every interactive element in the app resolves to a non-empty accessible name.
- The validator computes names through the standard resolution order rather than reading markup.
- Empty, generic, and duplicated names are reported as separate categories.
- No control produces a doubled announcement from conflicting attributes.
- Icon-only and composite controls each resolve to a single coherent phrase.
- Controls inside menus, dialogs, and drawers are covered by the audit.
- Names derived from record data hold up when the underlying record is untitled.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
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
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
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.