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 agentmods add rules/ivangrynenko/cursorrules/accessibility-standardsgit clone --depth 1 https://github.com/ivangrynenko/cursorrulesWhat 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 | $0.00000 | $0.00612 |
| Opus 5 | $0.00000 | $0.00306 |
| Sonnet 5 | $0.00000 | $0.00122 |
| Haiku 4.5 | $0.00000 | $0.00061 |
Grade A, and why
accessibility-standards 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 yesterday.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- accessibility-standards — 89% identical, 71 lines differ
How it starts
The opening of the file, as written. The whole thing — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Standards
Ensures WCAG compliance and accessibility best practices.
Rule Details
-
Name: accessibility_standards
-
Description: Enforce accessibility standards and WCAG compliance
Filters
- file extension pattern:
"\\.(vue|jsx|tsx|html|php|css|scss|sass)$" # Expanded to include CSS files
Enforcement Checks
- Conditions:
- pattern
<img[^>]+(?!alt=)[^>]*>– Images must have alt attributes for screen readers. - pattern
aria-[a-z]+=\"\"– ARIA attributes should not be empty; provide meaningful values. - pattern
<button[^>]*>(?![^<]*[^\\s])[^<]*</button>– Buttons should have meaningful, descriptive content. - pattern
<a[^>]*href=\"#[^\"]*\"[^>]*>(?![^<]*<svg)[^<]*</a>– Links with href='#' should either be removed or have an aria-label for context. - pattern
<input[^>]+type=\"(text|email|password|search|tel|url)\"[^>]*>– negatedaria-label|aria-labelledby|title– Form inputs should include an aria-label or aria-labelledby attribute for better screen reader support. - pattern
<video[^>]*>(?!<track)[^<]*</video>– Videos should include captions for accessibility.
- pattern
Suggestions
- Guidance: Accessibility Best Practices:
- Heading Hierarchy: Use headings (h1 to h6) in a logical order to structure content.
- Keyboard Navigation: Ensure all interactive elements are accessible via keyboard.
- Semantic HTML: Favor semantic elements like , , , and for better structure comprehension.
- Color Contrast: Check color contrast ratios meet WCAG guidelines (4.5:1 for normal text, 7:1 for large text).
- Skip Navigation Links: Provide 'skip to main content' links for keyboard users to bypass repetitive navigation.
- Focus Management: Ensure focus indicators are visible and manage focus for modal dialogs or dynamic content changes.
- Form Labels: Associate labels with form controls using the 'for' attribute or wrap controls with .
- Descriptive Links: Use descriptive text for links, avoiding generic phrases like "click here."
- Touch Targets: Ensure touch target sizes are large enough (at least 44x44 pixels) for mobile users.
- Timeouts: Avoid or provide options to extend time limits where possible, or warn users before session expiry.
- Language Attribute: Set the lang attribute on the element to indicate the primary language of the page.
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.
- yesterday First seen · 45 lines · 612 tokens per session scan A affed8503430
accessibility-standards is a cursor rule published in the GitHub repository ivangrynenko/cursorrules (87 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 612 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-08-30.
Other cursor rules, from other repositories
angular
Angular: signals, standalone components, RxJS patterns.
django
Django: models, views, ORM best practices.
java
Modern Java: records, sealed classes, streams, virtual threads.
javascript
Modern JavaScript: ES2023+, async patterns, common traps.
rust
Rust patterns: ownership, Result types, iterators.
accessibility
Accessibility: semantic HTML, ARIA, keyboard navigation, testing.