intent-ref-accessibility-foundations

intent-ref-accessibility-foundations is a cursor rule for Cursor from ghaida/intent. It costs 3,391 tokens per session, scanned A, original, CC0-1.0.

A guide to designing products that people with different abilities can use, including people who rely on screen readers, keyboards, captions, or other assistive technology. It is based on WCAG 2.2, the Web Content Accessibility Guidelines.

In plain words
What is it for?
Use it for accessibility reviews, inclusive interface design, screen-reader support, keyboard navigation, readable content, alternative text, captions, and testing with assistive technology.
Why use it?
It helps find barriers that may prevent people from seeing, hearing, understanding, or operating an interface. It turns accessibility from a late compliance check into part of the design and testing process.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it for accessibility reviews, inclusive interface design, screen-reader support, keyboard navigation, readable content, alternative text, captions, and testing with assistive technology.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/ghaida/intent/intent-ref-accessibility-foundations
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/ghaida/intent

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 intent-ref-accessibility-foundations

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

Your own site · 80×15
<a href="https://agentmods.dev/rules/ghaida/intent/intent-ref-accessibility-foundations"><img src="https://agentmods.dev/badge/rules/ghaida/intent/intent-ref-accessibility-foundations.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 3,391 This file is loaded in full into every session.
When invoked 3,391 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.03391 $0.03391
Opus 5.5 $0.01356 $0.01356
Sonnet 5.5 $0.00678 $0.00678
Haiku 4.5 $0.00339 $0.00339

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

Security

Grade A, and why

intent-ref-accessibility-foundations 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.

.cursor/rules/intent-ref-accessibility-foundations.mdc · 200 lines

How it starts

The opening of the file, as written. The whole thing — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Accessibility Foundations

WCAG 2.2 for Designers

The Web Content Accessibility Guidelines are organized around four principles: Perceivable, Operable, Understandable, Robust (POUR). Most designers encounter WCAG as a compliance checklist. That's the wrong frame. WCAG is a design specification — it tells you what your design must achieve for the full spectrum of human ability.

Perceivable

Information and interface components must be presentable to users in ways they can perceive. This means: not everyone sees, not everyone hears, not everyone processes information the same way.

Text alternatives (1.1): Every non-text element that conveys information needs a text equivalent. Images need alt text. Icons need labels. Charts need data tables or summaries. Video needs captions and audio description. The question is always: if this visual element disappeared, would the user lose information?

How designers get this wrong: Decorative images with verbose alt text (screen readers will read "stock photo of a diverse team collaborating in a modern office" for every page — exhausting). Informative images with empty alt text. Complex charts with alt text that says "chart" instead of describing the data. Icons without any programmatic label. The fix is intentional alt text: describe what the image communicates, not what it depicts.

Time-based media (1.2): Video needs captions (synchronized text of spoken content) and audio description (narration of visual content). Audio needs transcripts. Live content needs real-time captions. This isn't just for deaf users — captions serve anyone in a noisy or quiet environment.

Adaptable (1.3): Information structure must be programmatic, not just visual. A heading that's bold and large but coded as a <div> is invisible to screen readers. A data table that's built with positioned divs instead of <table> elements loses its row/column relationships. Design decisions about hierarchy, grouping, and sequence must be implementable as semantic structure.

Read the full file on GitHub · 200 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 · 200 lines · 3,391 tokens per session scan A 748e08f026ef

Subscribe to this mod's changes

intent-ref-accessibility-foundations is a cursor rule published in the GitHub repository ghaida/intent (214 stars, last pushed 7d ago), licensed CC0-1.0. It adds 3,391 tokens to every session, about $0.0136 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.