Landmark Shell
Give every page the same navigable regions so people can jump straight to the content.
What it adds
A reusable application shell providing labelled banner, navigation, main, complementary, and contentinfo regions on every route.
What your agent is told to do
5
What your agent is told to do
5-
1
Find the layouts the app already renders and identify what each region actually is — the top bar, the primary navigation, the page body, any inspector or sidebar, the footer — then express them as landmarks once in the shell rather than per page.
-
2
Give the shell exactly one main region per rendered page, and make it the target of a skip link that is the first focusable thing in the document.
-
3
Label every landmark that appears more than once so they can be told apart — primary navigation, breadcrumb, pagination — using a short distinct name rather than the word navigation repeated.
-
4
Move focus to the main region's heading on route change so keyboard and screen reader users start at the new content rather than back at the top of the navigation, and keep the announcement itself in Live Region Manager rather than adding a second mechanism here.
-
5
Do not achieve the visual arrangement by reordering with layout properties while leaving the source order wrong. Tab order and reading order follow the source, so a sidebar that reads before the main content in source but sits to the right on screen will confuse everyone who does not use a mouse.
Edge cases it handles
7
Edge cases it handles
7- There must be exactly one main region at any moment. A nested layout that renders its own main inside the shell's produces two, and assistive technology then offers the user a meaningless choice.
- Multiple navigation regions without distinct labels are indistinguishable in a landmark list; every repeated landmark type needs its own accessible name, and those names must not duplicate each other.
- Visual order and source order must agree. Where a responsive layout moves a region, the source must move with it rather than being repositioned visually only.
- Route changes that mount a new shell alongside the old one during a transition will briefly duplicate every landmark id and label; ensure the outgoing tree is removed before the incoming one is announced, and generate ids that cannot collide across two mounted instances.
- Modals and fullscreen surfaces must hide the rest of the shell from assistive technology while open, or the user can arrow out of the dialog into the page behind it.
- A page with no sidebar or no footer must omit that landmark entirely rather than render an empty labelled region.
- The skip link must actually move focus, not merely scroll — a hash change that leaves focus at the top of the document does nothing for keyboard users.
Definition of done
9
Definition of done
9- Every route renders exactly one main landmark, wrapped by the shared shell.
- Banner, navigation, main, complementary, and contentinfo regions are present where they apply and absent where they do not.
- Repeated landmark types each carry a distinct accessible name.
- A skip link is the first focusable element and moves focus into main.
- Source order matches visual order at every breakpoint.
- No duplicate ids or duplicate landmarks exist at any point during a route transition.
- An open modal hides the shell from assistive technology until it closes.
- The feature matches the existing design system.
- No existing functionality is broken.
Related features
Screen Reader Only Utility
Screen Reader Only Utility
One tested way to add text for assistive technology without it appearing on screen.
What it does
A single visually hidden utility used for labels, instructions, and context that assistive technology needs and sighted users do not.
How it works
- 1 Find every place the app currently hides text from sight — off-screen positioning, zero dimensions, transparent colour, tiny font sizes, aria-label strings duplicating nearby copy — and consolidate them onto one utility.
- 2 Build it by clipping the element to nothing while keeping it rendered and in the accessibility tree: it must occupy no visual space and contribute nothing to layout, yet still be read in document order.
- 3 Provide a second variant that becomes visible when it receives focus, and use it for skip links and any other hidden content that is itself focusable.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/screen-reader-only-utility
Progress Indicator System
Progress Indicator System
Tell people how far along the work is, in the same way every time.
What it does
A consistent set of bars, rings, step trackers, and accompanying text for work that takes measurable time.
How it works
- 1 Identify every operation in the app that takes long enough to need feedback — uploads, imports, exports, batch actions, multi-step flows — and decide for each whether its progress is genuinely measurable.
- 2 Use a determinate form only when a real proportion is known. Where the total is unknown, use an indeterminate form and say what is happening in words rather than inventing a percentage.
- 3 Pair every indicator with text that names the operation and its current position, so the information survives for someone who cannot see the graphic.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/progress-indicator-system
Avatar Group
Avatar Group
Show who is involved in a compact space without a pile of broken images.
What it does
A stacked set of member avatars with deterministic ordering, an overflow count, and access to the full list.
How it works
- 1 Find the places that show several people at once — assignees, collaborators, workspace members, comment participants — and render them through one grouped component.
- 2 Order the stack deterministically by a stable rule such as role then name, so the same group renders in the same order on every load and every device.
- 3 Cap the number shown and collapse the remainder into a single count that is announced meaningfully, not as a bare number sitting after a row of pictures.
Copy the prompt
No account needed
Add this feature to my app:
https://addthisfeature.com/x/avatar-group
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.