aria-fix

A set of fixes for making web components easier to use with keyboards and screen readers through correct HTML and ARIA attributes.

In plain words
What is it for?
Use it to repair interactive controls, dialogs, forms, dynamic messages, headings, navigation landmarks, and other web accessibility issues.
Why use it?
It addresses missing labels, roles, states, focus behavior, keyboard actions, form connections, and page structure that can make interfaces inaccessible.

Command

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.

agentmods
npx agentmods add commands/rohitg00/awesome-claude-code-toolkit/aria-fix
Clone the repo
git clone --depth 1 https://github.com/rohitg00/awesome-claude-code-toolkit
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 451 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00015 $0.00451
Opus 5 $0.00008 $0.00226
Sonnet 5 $0.00003 $0.00090
Haiku 4.5 $0.00002 $0.00045

Measured yesterday against content hash f5f13f0183bb, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

plugins/accessibility-checker/commands/aria-fix.md · 52 lines

What it actually says

Fix ARIA attributes and accessibility issues in web components.

Steps

  1. Read the target component and identify accessibility issues.
  2. Apply ARIA fixes by category:
    • Roles: Add role attributes to custom interactive elements.
    • States: Add aria-expanded, aria-selected, aria-checked for stateful components.
    • Properties: Add aria-label, aria-describedby, aria-labelledby.
    • Live regions: Add aria-live for dynamic content updates.
  3. Fix interactive element accessibility:
    • Add tabIndex={0} to custom interactive elements.
    • Add keyboard event handlers (onKeyDown for Enter/Space).
    • Ensure focus is visible with proper styling.
    • Trap focus in modal dialogs.
  4. Fix form accessibility:
    • Associate labels with inputs.
    • Add aria-invalid and aria-describedby for validation errors.
    • Group related fields with fieldset and legend.
  5. Fix semantic HTML:
    • Replace div click handlers with button elements.
    • Use proper heading hierarchy (h1 > h2 > h3).
    • Use landmark elements (nav, main, aside, footer).
  6. Verify fixes do not break existing functionality.

Format

ARIA Fixes Applied: <file>

Changes:
  - L<N>: Added role="button" and keyboard handler to clickable div
  - L<N>: Added aria-label="Close dialog" to icon button
  - L<N>: Added aria-live="polite" to status message container
  - L<N>: Replaced div with semantic <nav> element

Tests: verify with keyboard navigation and screen reader

Rules

  • Prefer semantic HTML over ARIA attributes (a button over div with role=button).
  • Never use aria-hidden="true" on focusable elements.
  • Ensure every ARIA role has the required states and properties.
  • Test keyboard navigation order matches visual order.
  • Do not add ARIA attributes that duplicate native HTML semantics.
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. yesterday First seen · 52 lines · 15 tokens per session scan A f5f13f0183bb

Subscribe to this mod's changes

aria-fix is a command published in the GitHub repository rohitg00/awesome-claude-code-toolkit (2,570 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 15 tokens to every session and 451 once invoked, about $0.0001 per session on Opus 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.