accessibility-testing

accessibility-testing is a skill for Claude Code from summarybotng/summarybot-ng. It costs 50 tokens per session (1,632 once invoked), scanned A, original, MIT.

A process for checking whether software works for people with disabilities and follows WCAG 2.2 accessibility guidance.

In plain words
What is it for?
Use it for accessibility audits, release checks, screen-reader and keyboard testing, and compliance work.
Why use it?
It helps find barriers such as missing labels, poor color contrast, invisible focus, and unusable keyboard navigation.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it for accessibility audits, release checks, screen-reader and keyboard testing, and compliance work.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/summarybotng/summarybot-ng/accessibility-testing
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.

Any agent
npx skills add summarybotng/summarybot-ng --skill accessibility-testing
Clone the repo
git clone --depth 1 https://github.com/summarybotng/summarybot-ng

Made for: Claude Code.

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/summarybotng/summarybot-ng/accessibility-testing/github.svg)](https://agentmods.dev/skills/summarybotng/summarybot-ng/accessibility-testing)
Your own site
<a href="https://agentmods.dev/skills/summarybotng/summarybot-ng/accessibility-testing"><img src="https://agentmods.dev/badge/skills/summarybotng/summarybot-ng/accessibility-testing/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-testing

Your own site · 80×15
<a href="https://agentmods.dev/skills/summarybotng/summarybot-ng/accessibility-testing"><img src="https://agentmods.dev/badge/skills/summarybotng/summarybot-ng/accessibility-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,632 The whole file, excluding the scripts and references it only reads on demand.
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.00050 $0.01632
Opus 5.5 $0.00020 $0.00653
Sonnet 5.5 $0.00010 $0.00326
Haiku 4.5 $0.00005 $0.00163

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

Security

Grade A, and why

accessibility-testing 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.

.claude/skills/accessibility-testing/SKILL.md · 224 lines

How it starts

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

Accessibility Testing

<default_to_action> When testing accessibility or ensuring compliance:

  1. APPLY POUR principles: Perceivable, Operable, Understandable, Robust
  2. TEST with keyboard-only navigation (Tab, Enter, Escape)
  3. VALIDATE with screen readers (VoiceOver, NVDA, JAWS)
  4. CHECK color contrast (4.5:1 for text, 3:1 for large text)
  5. AUTOMATE with axe-core, integrate in CI/CD pipeline

Quick A11y Checklist:

  • All images have alt text (or alt="" for decorative)
  • All form fields have labels
  • Color is never the only indicator
  • Focus visible on all interactive elements
  • Keyboard navigation works throughout

Critical Success Factors:

  • Automated testing catches 30-50% of issues
  • Manual testing with real assistive tech required
  • Include users with disabilities in testing </default_to_action>

Quick Reference Card

When to Use

  • Legal compliance (ADA, Section 508, EU Directive)
  • New feature development
  • Before release validation
  • Accessibility audits

WCAG 2.2 Levels

Level Requirement Target
A Basic accessibility Minimum legal
AA Standard (most orgs) Industry standard
AAA Enhanced Specialized sites

POUR Principles

Principle Meaning Key Tests
Perceivable Can perceive content Alt text, contrast, captions
Operable Can operate UI Keyboard, no seizures, navigation
Understandable Can understand Clear labels, predictable, errors
Robust Works with assistive tech Valid HTML, ARIA

Color Contrast Requirements

Content AA Ratio AAA Ratio
Normal text 4.5:1 7:1
Large text (18pt+) 3:1 4.5:1
UI components 3:1 -

Keyboard Navigation Testing

// Test all interactive elements reachable via keyboard
test('all interactive elements keyboard accessible', async ({ page }) => {
  await page.goto('/');

  const focusableElements = await page.$$('button, a, input, select, textarea, [tabindex]');

  for (const element of focusableElements) {
    await element.focus();
    const isFocused = await element.evaluate(el => document.activeElement === el);
    expect(isFocused).toBe(true);
  }
});

// Verify visible focus indicator
test('focus indicator visible', async ({ page }) => {
  await page.goto('/');
  await page.keyboard.press('Tab');

  const focusedElement = await page.locator(':focus');
  const outline = await focusedElement.evaluate(el =>
    getComputedStyle(el).outline
  );

  expect(outline).not.toBe('none');
});

Read the full file on GitHub · 224 lines

Files

What ships with it

4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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 · 224 lines · 50 tokens per session scan A 06e56f1bc35d

Subscribe to this mod's changes

accessibility-testing is a skill published in the GitHub repository summarybotng/summarybot-ng (2 stars, last pushed 4mo ago), licensed MIT. It adds 50 tokens to every session and 1,632 once invoked, about $0.0002 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-09-03.

Related

Other skills, from other repositories

accessibility-testing

WCAG 2.2 compliance testing, screen reader validation, and inclusive design verification. Use when ensuring legal compliance (ADA, Section 508), testing for disabilities, or building accessible applications for 1 billion disabled users globally.

proffesor-for-testing/agentic-qe · 50 tokens

Accessibility Auditor

Comprehensive WCAG 2.1 AA compliance testing combining automated axe-core scans with manual keyboard navigation, screen reader compatibility, and focus management verification.

PramodDutta/qaskills · 32 tokens

Accessibility A11y Enhanced

Comprehensive WCAG compliance and accessibility testing covering ARIA, keyboard navigation, screen readers, color contrast, and automated a11y validation.

PramodDutta/qaskills · 34 tokens

accessibility-engineer

You are the Accessibility Engineering Specialist. You ensure digital products are usable by everyone, including people with visual, auditory, motor, and cognitive disabilities. You audit against WCAG 2.2 standards (AA minimum, AAA preferred), implement ARIA patterns, ensure keyboard navigability, test with screen…

buiphucminhtam/forgewright · 61 tokens

accessibility-commerce

Make your store usable by everyone with WCAG 2.1 AA compliance — screen reader support, keyboard navigation, and accessible cart and checkout flows.

finsilabs/awesome-ecommerce-skills · 33 tokens

accessibility-compliance-audit

Comprehensive web accessibility (a11y) audit and compliance skill. Audits HTML, React, Vue, and Angular codebases against WCAG 2.2 AA standards. Activates when users ask for "accessibility audit", "a11y check", "WCAG compliance", "ADA compliance", "screen reader testing", "keyboard navigation audit", "color contrast…

JPeetz/agent-skills · 134 tokens