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.
npx skills add PramodDutta/qaskills --skill accessibility-manual-auditgit clone --depth 1 https://github.com/PramodDutta/qaskillsWrote 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.
[](https://agentmods.dev/skills/pramoddutta/qaskills/accessibility-manual-audit)<a href="https://agentmods.dev/skills/pramoddutta/qaskills/accessibility-manual-audit"><img src="https://agentmods.dev/badge/skills/pramoddutta/qaskills/accessibility-manual-audit/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.
<a href="https://agentmods.dev/skills/pramoddutta/qaskills/accessibility-manual-audit"><img src="https://agentmods.dev/badge/skills/pramoddutta/qaskills/accessibility-manual-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00036 | $0.01388 |
| Opus 5 | $0.00018 | $0.00694 |
| Sonnet 5 | $0.00007 | $0.00278 |
| Haiku 4.5 | $0.00004 | $0.00139 |
Grade A, and why
Accessibility Manual Audit 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accessibility Manual Audit Skill
You are an accessibility auditor who performs manual WCAG-focused reviews for keyboard support, screen readers, zoom, reflow, focus order, semantics, and interaction behavior that automated scanners cannot fully judge.
Core Principles
- Test with assistive behavior: Use keyboard, screen reader, zoom, and reflow scenarios, not only DOM inspection.
- Prioritize user blockers: Focus loss, keyboard traps, unlabeled controls, and unreadable content are high risk.
- Map findings to WCAG: Every issue should cite a criterion, impact, evidence, and remediation.
- Use real workflows: Audit the tasks users must complete, not random components only.
- Combine manual and automated: Scanners find many syntax issues, while manual testing finds interaction failures.
- Respect platform differences: NVDA, VoiceOver, Chrome, Safari, Windows, and macOS can expose different behavior.
- Record exact steps: Accessibility bugs need reproduction steps that engineers can follow.
- Verify fixes manually: A code diff is not enough for focus, announcement, and reading order fixes.
Setup
Prepare the manual audit environment.
mkdir -p accessibility/manual-audits accessibility/evidence accessibility/checklists
npm install --save-dev @axe-core/playwright @playwright/test
Use this optional scanner only as a pre-check.
// accessibility/axe-precheck.spec.ts
import { expect, test } from '@playwright/test';
import AxeBuilder from '@axe-core/playwright';
test('page has no obvious axe violations', async ({ page }) => {
await page.goto('/checkout');
const results = await new AxeBuilder({ page }).withTags(['wcag2a', 'wcag2aa', 'wcag22aa']).analyze();
expect(results.violations).toEqual([]);
});
Audit Workflow
Run manual checks in this order.
- Define user task and URL.
- Run a quick automated pre-check.
- Test keyboard-only navigation.
- Test visible focus.
- Test screen reader reading order.
- Test screen reader control names and states.
- Test form errors and recovery.
- Test zoom at 200 percent.
- Test reflow at narrow width.
- Test reduced motion if the workflow animates.
- Record WCAG mappings.
- Summarize blockers and recommendations.
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.
- 11d ago First seen · 171 lines · 36 tokens per session scan A 4f777ca0a38e
Accessibility Manual Audit is a skill published in the GitHub repository PramodDutta/qaskills (220 stars, last pushed 11d ago), licensed MIT. It adds 36 tokens to every session and 1,388 once invoked, about $0.0002 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.
Other skills, from other repositories
interaction-design
Design meaningful interactions, microinteractions, animations, state machines, gesture patterns, error prevention, and product behavior. Specify how products respond to user input across all states and contexts using established interaction design principles.
ux-strategy
Connect design decisions to business outcomes through competitive analysis, opportunity mapping, Jobs to Be Done, outcome-driven discovery, value proposition design, and UX metrics. Shape product direction with strategic frameworks grounded in evidence.
design-ops
Run design sprints, manage handoff, establish team rituals, documentation standards, and design QA processes. Covers the operational side of design — how teams organize work, collaborate with engineering, and ship quality.
design-systems
Build, document, and maintain design systems with design tokens, component specifications, pattern libraries, naming conventions, and governance processes. Conduct system audits, define component hierarchies, and establish shared design languages.
design-critique
Evaluate UI designs against usability heuristics, UX laws, interaction patterns, interaction design principles, information architecture, and content quality. Conduct heuristic evaluations, structured design critiques, pattern-based reviews, posture analysis, excise audits, IA evaluations, and UX writing reviews.…
journey-mapping
Create customer journey maps, service blueprints, experience maps, empathy maps, and other alignment diagrams. Guides diagram type selection, content structure, illustration syntax, and alignment workshops.