accessibility-standards

accessibility-standards is a cursor rule for Cursor from ivangrynenko/cursorrules. It costs 612 tokens per session, scanned A, original, MIT.

A set of coding rules based on WCAG, the international guidelines for making websites usable by people with disabilities. It checks common HTML, CSS, Vue, JSX, and TSX patterns for accessibility problems.

In plain words
What is it for?
Use it while reviewing or writing front-end code to find accessibility issues in images, controls, forms, links, and videos.
Why use it?
It catches missing image descriptions, unclear buttons and links, empty ARIA labels, unlabeled form fields, and videos without captions before they reach users.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it while reviewing or writing front-end code to find accessibility issues in images, controls, forms, links, and videos.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/ivangrynenko/cursorrules/accessibility-standards
Install

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.

Clone the repo
git clone --depth 1 https://github.com/ivangrynenko/cursorrules

Made for: Cursor.

Wrote 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.

agentmods badge for accessibility-standards

README.md
[![agentmods](https://agentmods.dev/badge/rules/ivangrynenko/cursorrules/accessibility-standards/github.svg)](https://agentmods.dev/rules/ivangrynenko/cursorrules/accessibility-standards)
Your own site
<a href="https://agentmods.dev/rules/ivangrynenko/cursorrules/accessibility-standards"><img src="https://agentmods.dev/badge/rules/ivangrynenko/cursorrules/accessibility-standards/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.

agentmods 80×15 button for accessibility-standards

Your own site · 80×15
<a href="https://agentmods.dev/rules/ivangrynenko/cursorrules/accessibility-standards"><img src="https://agentmods.dev/badge/rules/ivangrynenko/cursorrules/accessibility-standards.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 612 This file is loaded in full into every session.
When invoked 612 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00612 $0.00612
Opus 5.5 $0.00245 $0.00245
Sonnet 5.5 $0.00122 $0.00122
Haiku 4.5 $0.00061 $0.00061

Measured 1mo ago against content hash affed8503430, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.cursor/rules/accessibility-standards.mdc · 45 lines

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)\"[^>]*> – negated aria-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.

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.

Read the full file on GitHub · 45 lines

Changes

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.

  1. 1mo ago First seen · 45 lines · 612 tokens per session scan A affed8503430

Subscribe to this mod's changes

accessibility-standards is a cursor rule published in the GitHub repository ivangrynenko/cursorrules (88 stars, last pushed 11mo ago), licensed MIT. It adds 612 tokens to every session, about $0.0024 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-30.