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.
git clone --depth 1 https://github.com/mhmdreza-rafiei/agent-toolsWrote 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/rules/mhmdreza-rafiei/agent-tools/accessibility)<a href="https://agentmods.dev/rules/mhmdreza-rafiei/agent-tools/accessibility"><img src="https://agentmods.dev/badge/rules/mhmdreza-rafiei/agent-tools/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/rules/mhmdreza-rafiei/agent-tools/accessibility"><img src="https://agentmods.dev/badge/rules/mhmdreza-rafiei/agent-tools/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.00025 | $0.00439 |
| Opus 5.5 | $0.00010 | $0.00176 |
| Sonnet 5.5 | $0.00005 | $0.00088 |
| Haiku 4.5 | $0.00003 | $0.00044 |
Grade A, and why
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 2mo 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
Accessibility
Applies when building or changing UI. Load for components, pages, forms. Not every chat. The floor is WCAG 2.2 AA — not a ceiling, a floor.
Keyboard
- Every interactive element is reachable and operable via keyboard.
- Visible focus on every focusable element; never remove the outline without replacing it.
- Logical tab order; no keyboard traps (a modal must trap and release cleanly).
Semantics & ARIA
- Use native semantics first (
button,nav,dialog). Add ARIA only where native semantics are missing or insufficient. aria-label/aria-labelledbyon icon-only buttons and ambiguous controls; never duplicate a visible label as anaria-label.- Live regions (
aria-live) for dynamic updates that a screen-reader user would otherwise miss.
Labels & names
- Every input has a visible
<label>(or equivalent). Noplaceholder-as-label. - Every interactive element has an accessible name.
- Required fields indicated programmatically (
required,aria-required), not by color or text alone.
Contrast & motion
- Text contrast ≥ 4.5:1 (normal), ≥ 3:1 (large). UI components and graphical objects ≥ 3:1.
- Respect
prefers-reduced-motion; no autoplaying motion that can't be paused.
Do not
- Ship a UI change without a keyboard check.
- Use color or icon alone to convey state — add text or
aria-label. - Add ARIA that duplicates native semantics (redundant
role="button"on a<button>).
Related
/audit/a11y— runs the audit that checks this rule.agents/qa/accessibility-auditor— owns the deeper fix work.
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.
- 2mo ago First seen · 55 lines · 25 tokens per session scan A d85cc6f42ac4
accessibility is a cursor rule published in the GitHub repository mhmdreza-rafiei/agent-tools (5 stars, last pushed 18d ago), licensed MIT. It adds 25 tokens to every session and 439 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-08-31.
Other cursor rules, from other repositories
prototype-previewer
Build interactive prototype reviewers with synced review notes and Figma capture pages.
figma-performance
Handling large documents efficiently in the Plugin API.
ant-design
A set of guidelines for using Ant Design, a collection of ready-made interface components, in React applications. It covers code organization, performance, security, testing, and common mistakes.
7-day-nextjs-web-design-cursor
A seven-day design workflow for web products that will be built in Next.js.
clone-ai
Site Clone AI — website klonlama pipeline kuralları.
mermaid
Diagram Creator. Load when the user requests "Create a diagram".