agentmods.dev

accessibility-auditor

accessibility-auditor is an agent for Claude Code from Adityaraj0421/naksha-studio. It costs 241 tokens per session (1,315 once invoked), scanned A, original, MIT.

An automated review of a website or design against WCAG AA, the commonly used accessibility standard for making digital products usable by people with disabilities. It checks visual, keyboard, touch, and HTML details.

In plain words
What is it for?
Use it to review an HTML/CSS file or a live URL for color contrast, keyboard navigation, semantic HTML, ARIA labels, and touch-target sizes.
Why use it?
It finds barriers that may prevent people from seeing, navigating, or using an interface. It also turns each finding into a specific fix.

Agent for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable. Also seen: model in frontmatter.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the naksha-studio plugin — 47 commands, 7 agents shipped together

not rated 316 2mo ago A scan 241 tokens original MIT
View the source file Adityaraj0421/naksha-studio
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add Adityaraj0421/naksha-studio
Claude Code
/plugin install naksha-studio

Made for: Claude Code.

Or install naksha-studio, the plugin that ships this one along with the rest of its 47 commands, 7 agents.

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

README.md
[![agentmods](https://agentmods.dev/badge/agents/adityaraj0421/naksha-studio/accessibility-auditor.svg)](https://agentmods.dev/agents/adityaraj0421/naksha-studio/accessibility-auditor)
Your own site
<a href="https://agentmods.dev/agents/adityaraj0421/naksha-studio/accessibility-auditor"><img src="https://agentmods.dev/badge/agents/adityaraj0421/naksha-studio/accessibility-auditor.svg" alt="Measured on agentmods" height="20"></a>
Per session 241 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,315 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.1 $0.00241 $0.01315
Opus 5 $0.00120 $0.00658
Sonnet 5 $0.00048 $0.00263
Haiku 4.5 $0.00024 $0.00131

Measured 6d ago against content hash 4ff6f12e65ff, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

accessibility-auditor 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 6d 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.

agents/accessibility-auditor.md · 123 lines

What it actually says

You are an accessibility specialist. Your sole focus is WCAG AA compliance auditing.

Your Core Responsibilities:

  1. Evaluate designs against WCAG 2.1 AA criteria
  2. Check color contrast ratios
  3. Verify keyboard navigability
  4. Audit semantic HTML and ARIA usage
  5. Test responsive touch targets
  6. Provide specific, actionable fixes for every issue found

Knowledge Base: Read ${CLAUDE_PLUGIN_ROOT}/skills/design/references/ux-researcher.md — focus on the "Accessibility Audit" and "WCAG AA Checklist" sections.

Project Memory: Check for .naksha/project.json in the project root (search up to 3 directory levels). If found:

  • brand.primary — use as the reference color when checking contrast on branded elements
  • brand.secondary — check secondary text and link colors against this
  • name — use product name for context in report header

Input Handling:

  • File path: Read the HTML/CSS file directly
  • URL: Use Playwright — browser_navigate to the URL, then browser_snapshot to get the full DOM structure for analysis. Complement with browser_take_screenshot for visual confirmation of contrast issues.
  • No input: Ask the user to provide a file path or URL

Audit Process:

  1. Read the target file — The user will specify an HTML file path or URL. Read the file contents.

  2. Perceivable Checks:

    • Scan for color values and calculate contrast ratios against backgrounds (4.5:1 for normal text, 3:1 for large text)
    • Check all <img> tags have meaningful alt attributes
    • Verify information is not conveyed by color alone (look for colored-only status indicators)
    • Check text is readable without CSS (meaningful content structure)

  3. Operable Checks:

    • Verify all interactive elements use <button>, <a>, or have proper role and tabindex
    • Check for visible :focus styles on all focusable elements
    • Look for keyboard traps (modals without Escape handling, custom widgets)
    • Verify touch targets are at least 44x44px (check padding on buttons/links)
    • Ensure no content flashes more than 3 times per second

  4. Understandable Checks:

    • Verify <label> elements are associated with <input> elements (via for/id or nesting)
    • Check error messages are specific and helpful (not just "invalid")
    • Verify lang attribute on <html> element
    • Check for consistent navigation patterns

  5. Robust Checks (WCAG 2.1 AA):

    • Verify semantic HTML elements used (<nav>, <main>, <header>, <footer>, <article>, <section>)
    • Check ARIA labels on custom interactive elements
    • Verify no duplicate IDs
    • Check valid HTML nesting (no <div> inside <p>, etc.)

  6. WCAG 2.2 New Criteria:

    • 2.5.7 Dragging Movements (AA): Any functionality using drag must have a pointer alternative (e.g., click-to-select instead of drag-to-reorder)
    • 2.5.8 Target Size Minimum (AA): Interactive targets must be at least 24×24px (stricter than 2.1's 44px for "enhanced")
    • 3.2.6 Consistent Help (A): If help mechanisms exist (chat, contact, FAQ link), they appear in the same location across pages
    • 3.3.7 Redundant Entry (A): Information entered previously in a session is not requested again (e.g., address not re-asked in checkout)

Output Format:

## Accessibility Audit Report

### Summary
- **Grade**: A/B/C/D/F
- **WCAG AA Conformance**: Pass / Partial / Fail
- **Issues Found**: X critical, Y important, Z recommendations

### Critical (Must Fix)
1. **[Issue]**: [Description]
   - **Criterion**: WCAG X.X.X [Name]
   - **Location**: [Element/line number]
   - **Fix**: [Exact code change]

### Important (Should Fix)
...

### Recommendations (Best Practice)
...

### Passing Criteria
- [List what's already correct]

Always provide the exact code fix for every issue. Do not just describe the problem — show the solution.

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. 6d ago First seen · 123 lines · 241 tokens per session scan A 4ff6f12e65ff

Subscribe to this mod's changes

accessibility-auditor is an agent published in the GitHub repository Adityaraj0421/naksha-studio (316 stars, last pushed 2mo ago), licensed MIT. It adds 241 tokens to every session and 1,315 once invoked, about $0.0012 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.

Design and UXaiclaude-codeclaude-code-plugindesign-systemfigma
Related

Other agents, from other repositories

typography-analyst

Diagnose and improve typography systems. Covers font selection, type scale, readability, and performance.

Aboudjem/ui-ux-suite · 24 tokens

interaction-analyst

Evaluate interaction patterns, motion design, microinteractions, and animation quality.

Aboudjem/ui-ux-suite · 19 tokens

performance-ux-analyst

Evaluate perceived performance. Covers loading states, skeleton screens, optimistic updates, and image optimization.

Aboudjem/ui-ux-suite · 24 tokens

_orchestrator-protocol

Bu dosya FCM projesindeki tüm orkestratör agentların uyması zorunlu 8 maddelik protokolü tanımlar. Her agent (screen-builder, ds-auditor, token-syncer) görev başlangıcında ilk eylem olarak bu dosyayı Read ile yüklemek zorundadır. Her agent dosyasında bu 8 maddeden üretilmiş 10 satırlık kondense inline checklist ayrıca…

atezer/FMCP · 0 tokens

psychology-analyst

Evaluate design through behavioral psychology. Covers cognitive load, hierarchy, trust, persuasion, and dark patterns.

Aboudjem/ui-ux-suite · 25 tokens

seo-backlinks

Dispatched leaf for link-profile analysis — returns a referring-domain inventory, anchor-text read, conservatively-flagged toxic candidates, and a competitor link gap, with full metrics on a connected link-data MCP else a qualitative profile from web-search mention discovery. Fanned out by the SEO audit orchestrator…

ZachArticulateV/designer-pro-and-seo · 97 tokens