accessibility

accessibility is a cursor rule for Cursor from thematters/matters-web. It costs 556 tokens per session, scanned A, original, Apache-2.0.

A set of web accessibility rules for making pages usable by people with different abilities, including guidance on meaningful HTML elements and ARIA labels.

In plain words
What is it for?
Use it when building or reviewing web pages, especially headings, navigation, buttons, links, images, dialogs, and alerts.
Why use it?
It reduces the chance that page structure and controls are unclear to screen readers or other assistive tools.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit Use it when building or reviewing web pages, especially headings, navigation, buttons, links, images, dialogs, and alerts.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/thematters/matters-web/accessibility
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/thematters/matters-web

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

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

agentmods 80×15 button for accessibility

Your own site · 80×15
<a href="https://agentmods.dev/rules/thematters/matters-web/accessibility"><img src="https://agentmods.dev/badge/rules/thematters/matters-web/accessibility.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 556 This file is loaded in full into every session.
When invoked 556 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.00556 $0.00556
Opus 5.5 $0.00222 $0.00222
Sonnet 5.5 $0.00111 $0.00111
Haiku 4.5 $0.00056 $0.00056

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

Security

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.

.cursor/rules/accessibility.mdc · 71 lines

How it starts

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

Accessibility (A11Y)

Matters Web follows these accessibility best practices to ensure the platform is usable by everyone.

Semantic HTML

Use semantic HTML elements to provide meaning and structure:

  • <header>: Page header or section header
  • <nav>: Navigation menus
  • <main>: Main content area
  • <section>: Standalone section of content
  • <article>: Self-contained composition (e.g., blog post)
  • <aside>: Content tangentially related to the content around it
  • <footer>: Footer for page or section
  • <figure> and <figcaption>: Images with captions
  • <button>: For interactive elements that perform an action
  • <a>: Only for navigation to a new page or location within page

Non-semantic elements like <div> and <span> should only be used when no semantic element is appropriate.

WAI-ARIA

Use ARIA attributes when HTML semantics aren't sufficient:

  • role: Define the purpose of an element (e.g., role="alert", role="dialog")
  • aria-label: Provide an accessible name (e.g., aria-label="Close dialog")
  • aria-labelledby: Reference another element as the label
  • aria-describedby: Reference descriptive text for an element
  • aria-expanded: Indicate if expandable element is open or closed
  • aria-hidden: Hide decorative elements from screen readers
  • aria-live: For dynamically updating content

Focus Management

  • Ensure all interactive elements are keyboard accessible
  • Maintain a logical tab order
  • Make focus visible with clear focus indicators
  • Trap focus inside modals with <FocusLock> component by react-focus-lock

Images

  • Always include alt text for images
  • Use empty alt="" for decorative images

Forms

  • Associate labels with form controls using htmlFor
  • Group related form elements with <fieldset> and <legend>
  • Provide clear error messages and validation
  • Use appropriate input types (e.g., type="email")

Components

Our accessible components include:

  • <Button>: Accessible button component
  • <Dialog>: Accessible modal dialog with focus management
  • <Form>: Accessible form controls with proper labeling

Read the full file on GitHub · 71 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 · 71 lines · 556 tokens per session scan A f28d22e3395a

Subscribe to this mod's changes

accessibility is a cursor rule published in the GitHub repository thematters/matters-web (86 stars, last pushed 5d ago), licensed Apache-2.0. It adds 556 tokens to every session, about $0.0022 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.