Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add SalesforceCommerceCloud/b2c-developer-tooling --skill sfnext-accessibilitygit clone --depth 1 https://github.com/SalesforceCommerceCloud/b2c-developer-toolingWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/salesforcecommercecloud/b2c-developer-tooling/sfnext-accessibility)<a href="https://agentmods.dev/skills/salesforcecommercecloud/b2c-developer-tooling/sfnext-accessibility"><img src="https://agentmods.dev/badge/skills/salesforcecommercecloud/b2c-developer-tooling/sfnext-accessibility/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/salesforcecommercecloud/b2c-developer-tooling/sfnext-accessibility"><img src="https://agentmods.dev/badge/skills/salesforcecommercecloud/b2c-developer-tooling/sfnext-accessibility.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00209 | $0.02096 |
| Opus 5.5 | $0.00084 | $0.00838 |
| Sonnet 5.5 | $0.00042 | $0.00419 |
| Haiku 4.5 | $0.00021 | $0.00210 |
Grade A, and why
sfnext-accessibility scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 15d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Storefront Next Accessibility
Target: WCAG 2.1 AA. Accessibility is checked at three levels, cheapest first:
| Level | Tool | Catches |
|---|---|---|
| Lint | OxLint jsx-a11y (pnpm lint, pnpm lint:a11y) |
Missing alt/labels, invalid ARIA, non-interactive handlers, ambiguous link text |
| Component | Storybook a11y addon (axe) and play() assertions |
Contrast and name/role issues in a rendered state; focus, live regions, dialog behavior |
| Page | e2e axe scan (pnpm a11y) against e2e/a11y-baseline.json |
Page composition, layout, mobile vs desktop |
Some things no scanner finds: focus order, meaning carried by color alone, 200%/400% zoom reflow, and what a screen reader actually announces. Those need keyboard testing, a story play() assertion of the DOM facts behind them, or a human with assistive technology.
Author accessibly by default
- Use the project's building blocks; they are already accessible in the general case:
- Radix-based primitives in
src/components/ui/(dialog, dropdown-menu, sheet, tooltip, ...). FormLabel/FormControl/FormMessagefrom@/components/ui/formand the wrappers insrc/components/form-fields/(they wirearia-describedbyand invalid state from form context).src/components/product-imageandsrc/components/dynamic-image(alt text),src/components/radio-card(grouped options),src/components/skip-link.tsx(first focusable element, targets#main-content),src/components/announcement-banner.
- Radix-based primitives in
- Icon-only controls need a translated accessible name:
<Button aria-label={t('close')}>. Decorative icons getaria-hidden="true"and must not be focusable. - Every input needs a real label; errors must be programmatically associated and announced (form-field wrappers do this).
- Use semantic elements first (
button,a,ul,h1..h6); add ARIA only to fill gaps. Keep oneh1per page and do not skip levels. - Status changes that happen without navigation (cart updates, promo applied, errors) need an
aria-liveregion (role="status"orrole="alert"); the message must be rendered into an existing live region or the region must exist before content changes. - Dialogs and drawers: focus moves in on open, is trapped, returns to the trigger on close,
Escapecloses. Use the Radix dialog primitives rather than hand-rolling. - Respect
prefers-reduced-motion(seesrc/components/fade-through-imageandproduct-zoom-modalfor the pattern). - Keep visible focus styles; do not remove outlines without a replacement from the theme tokens.
- Do not "fix"
role="list"on aul: it is deliberate (Tailwind'slist-style: noneremoves list semantics in Safari + VoiceOver), and the lint config allows it.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 15d ago First seen · 104 lines · 209 tokens per session scan A 98b843b95557
sfnext-accessibility is a skill published in the GitHub repository SalesforceCommerceCloud/b2c-developer-tooling (56 stars, last pushed today), licensed Apache-2.0. It adds 209 tokens to every session and 2,096 once invoked, about $0.0008 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-05.
Other skills, from other repositories
frontend-design
Produce intentional, responsive, accessible UI work and perform visual QA instead of generic component assembly.
ambience-skill
Layer A ambience-and-typographic-motion reference anchored to the react-bits catalog (reactbits.dev). Stacks on any style skill whenever work adds a hero atmosphere, an animated or shader background, a typographic reveal (split, blur, shimmer, typewriter, count-up, marquee), scroll storytelling, or card surface…
interaction-skill
Layer A interaction-mechanics reference anchored to the beui.dev catalog. Stacks on any style skill whenever work adds or changes motion or interaction — micro-interactions, animated components, transitions, gestures, hover/press/state feedback, loading/success/error morphs, 'make it feel alive'. Mandates reading the…
designlang-tokens
Use when styling UI for cal.com — references the extracted design system tokens instead of inventing colors, spacing, or typography.
design-color
Add strategic color to monochromatic or dull interfaces using oklch for perceptually uniform palettes. Generates harmonious color systems with automatic light/dark variants and accessible contrast ratios.
accessibility
Use when making a web UI conform to WCAG 2.2 Level AA — axe-core or Lighthouse a11y violations, keyboard operability, focus management, ARIA roles/names/live regions, contrast, tap-target size. NOT palette or visual intent (that is design), NOT test-runner setup (that is testing-web), NOT LCP/page-speed (that is…