Borrowing it
Nothing to install: this file belongs to leboncoin/spark-web. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/leboncoin/spark-web/main/.cursor/skills/check-accessibility/SKILL.mdgit clone --depth 1 https://github.com/leboncoin/spark-webWrote 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/leboncoin/spark-web/check-accessibility)<a href="https://agentmods.dev/skills/leboncoin/spark-web/check-accessibility"><img src="https://agentmods.dev/badge/skills/leboncoin/spark-web/check-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/leboncoin/spark-web/check-accessibility"><img src="https://agentmods.dev/badge/skills/leboncoin/spark-web/check-accessibility.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00033 | $0.00462 |
| Opus 5.5 | $0.00013 | $0.00185 |
| Sonnet 5.5 | $0.00007 | $0.00092 |
| Haiku 4.5 | $0.00003 | $0.00046 |
Grade A, and why
check-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 1mo 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.
What it actually says
Check Accessibility
Verify that components meet WCAG 2.1 AA accessibility standards.
When to Use
- User wants to check accessibility
- User mentions "a11y", "accessibility", or "WCAG"
- Component has accessibility issues
- Before submitting a PR
Instructions
-
Automated Testing:
# Test all components npm run test:a11y # Test specific component(s) npm run test:a11y -- tabs npm run test:a11y -- tabs button card # Combine with Playwright options npm run test:a11y -- tabs --workers 1This runs Playwright tests with
@axe-core/playwrightfor automated accessibility checks. You can test specific components by passing their names as arguments after--. Component names are case-insensitive and should match the keys ine2e/a11y/routes/components.ts. -
Manual Checks:
- Verify semantic HTML elements
- Check ARIA attributes are correct
- Test keyboard navigation
- Verify focus management
- Test with screen readers
-
Common Accessibility Requirements:
- All interactive elements must be keyboard accessible
- Proper ARIA labels and roles
- Focus indicators visible
- Color contrast meets WCAG AA (4.5:1 for text)
- Semantic HTML structure
-
Testing Tools:
@axe-core/playwrightfor automated testing@testing-library/reactfor unit test accessibility- Browser DevTools Accessibility panel
- Screen reader testing (NVDA, JAWS, VoiceOver)
-
Fix Issues:
- Add missing ARIA attributes
- Fix keyboard navigation
- Improve focus management
- Fix color contrast
- Use semantic HTML
Standards
All components must meet WCAG 2.1 AA standards. See .cursor/rules/accessibility-standards.md for details.
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.
- 1mo ago First seen · 65 lines · 33 tokens per session scan A 5cf40511b432
check-accessibility is a skill published in the GitHub repository leboncoin/spark-web (94 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 462 once invoked, about $0.0001 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-09-05.
Other skills, from other repositories
test-component
Runs, analyzes, and fixes cross-framework interaction, visual-snapshot, aria-snapshot, and accessibility tests for a specific DB UX component's showcase pages.
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…
next-partial-prefetching-optimizer
Optimize what selected Next.js client navigations include before the click under Partial Prefetching. Use after Cache Components and Partial Prefetching are adopted when the user wants selected URL-specific UI to be instant, wants reusable content to wait for navigation, or needs to choose between default, viewport…
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
chakra-ui-migrate
Migrate Chakra UI projects from v2 to v3, covering package changes, codemods, provider setup, color mode, prop renaming, compound components, theming, recipes, and Next.js updates. Use this skill whenever a user is upgrading Chakra UI versions, encountering breaking changes after an upgrade, converting old v2 patterns…
chakra-ui-refactor
Review, convert, and improve UI code using Chakra UI v3. Use this skill whenever a user wants to review Chakra UI code for issues, convert plain HTML/CSS, Tailwind, CSS Modules, or styled-components to Chakra UI, clean up messy Chakra components, fix layout structure or token usage, or asks anything like "is this…