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/girijashankarj/cursor-handbookWrote 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/girijashankarj/cursor-handbook/accessibility)<a href="https://agentmods.dev/rules/girijashankarj/cursor-handbook/accessibility"><img src="https://agentmods.dev/badge/rules/girijashankarj/cursor-handbook/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/girijashankarj/cursor-handbook/accessibility"><img src="https://agentmods.dev/badge/rules/girijashankarj/cursor-handbook/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.00000 | $0.00451 |
| Opus 5.5 | $0.00000 | $0.00180 |
| Sonnet 5.5 | $0.00000 | $0.00090 |
| Haiku 4.5 | $0.00000 | $0.00045 |
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 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
Accessibility Rules
WCAG 2.1 AA Compliance (Minimum)
Semantic HTML
- Use semantic elements:
<nav>,<main>,<article>,<section>,<aside> - Use heading hierarchy:
<h1>→<h2>→<h3>(never skip levels) - Use
<button>for actions,<a>for navigation — never swap them - Use
<label>for all form inputs withhtmlForattribute - Use
<fieldset>and<legend>for related form groups
ARIA Attributes
- Add
aria-labelto icon-only buttons - Use
aria-liveregions for dynamic content updates - Add
roleattributes when semantic HTML isn't sufficient - Use
aria-expandedfor collapsible sections - Use
aria-describedbyfor complex form validation messages
Keyboard Navigation
- All interactive elements MUST be keyboard accessible
- Visible focus indicators on all focusable elements
- Logical tab order (avoid
tabIndex> 0) - Escape key closes modals and dropdowns
- Enter/Space activates buttons and links
Visual
- Minimum contrast ratio: 4.5:1 for normal text, 3:1 for large text
- Don't convey information through color alone — use icons or text
- Support text zoom up to 200% without loss of content
- Provide text alternatives for all images:
altattribute - Animated content must be pausable
Forms
- Clear error messages linked to the field via
aria-describedby - Required fields marked with
aria-required="true" - Form validation errors announced to screen readers
- Autofill support for common fields (name, email, address)
Testing
- Test with keyboard navigation
- Test with screen readers (VoiceOver, NVDA)
- Use axe-core or Lighthouse for automated a11y audits
- Include a11y tests in CI pipeline
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 · 50 lines · 0 tokens per session scan A cb238ebef319
accessibility is a cursor rule published in the GitHub repository girijashankarj/cursor-handbook (33 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 451 tokens. 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-03.
Other cursor rules, from other repositories
components
Component patterns and UI conventions.
tailwind
Tailwind CSS and styling conventions.
shadcn-ui
Cursor rule "shadcn-ui" from nedcodes-ok/cursorrules-collection, covering shadcn/ui rules, component usage, styling, forms and dialog/sheet/modal patterns.
nextjs-react-tailwind-cursorrules-prompt-file
Cursor rules for Next.js development with React and Tailwind CSS integration.
react-components-creation-cursorrules-prompt-file
Cursor rules for React component creation and development.
react-styled-components-cursorrules-prompt-file
Cursor rules for React development with Styled Components integration.