agentmods.dev

accessibility-testing-strategy

accessibility-testing-strategy is a skill for Claude Code from Owl-Listener/inclusive-design-skills. It costs 87 tokens per session (883 once invoked), scanned A, original, MIT.

A planning guide for testing whether websites and apps are accessible to people with disabilities. It combines automated checks, expert review, keyboard and screen-reader testing, zoom checks, and content review.

In plain words
What is it for?
Use it to create an accessibility test plan, decide what belongs in automated checks or manual review, set up testing in continuous integration, and plan final quality assurance.
Why use it?
Automated tools find only some accessibility problems, while human testing is needed for focus order, understandable content, and usable interactions. The guide helps teams choose appropriate tests, timing, and testers.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the accessibility-decisions plugin — 9 skills shipped together

not rated 108repo 5mo ago A scan 87 tokens original MIT

Good fit Use it to create an accessibility test plan, decide what belongs in automated checks or manual review, set up testing in continuous integration, and plan final quality assurance.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/owl-listener/inclusive-design-skills/accessibility-testing-strategy
View source ↗ Owl-Listener/inclusive-design-skills
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 Owl-Listener/inclusive-design-skills --skill accessibility-testing-strategy
Clone the repo
git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills

Made for: Claude Code.

Or install accessibility-decisions, the plugin that ships this one along with the rest of its 9 skills.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/owl-listener/inclusive-design-skills/accessibility-testing-strategy"><img src="https://agentmods.dev/badge/skills/owl-listener/inclusive-design-skills/accessibility-testing-strategy.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 87 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 883 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.00087 $0.00883
Opus 5.5 $0.00035 $0.00353
Sonnet 5.5 $0.00017 $0.00177
Haiku 4.5 $0.00009 $0.00088

Measured 2mo ago against content hash 51f905302a67, 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-strategy 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 2mo 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.

accessibility-decisions/skills/accessibility-testing-strategy/SKILL.md · 125 lines

How it starts

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

Accessibility Testing Strategy

Plan a testing approach that catches real accessibility barriers — because automated tools find roughly 30% of issues. The other 70% require human judgment.

The Testing Pyramid

Layer 1: Automated Testing (Catches ~30%)

What it finds:

  • Missing alt text
  • Colour contrast failures
  • Missing form labels
  • Missing language attribute
  • Empty headings and buttons
  • Duplicate IDs

What it misses:

  • Whether alt text is meaningful
  • Whether focus order is logical
  • Whether content makes sense
  • Whether interactions work with keyboard
  • Whether the experience is usable

Tools: axe, Lighthouse, WAVE, Pa11y, jest-axe When: on every build, in CI/CD pipeline Who: automated — no human needed

Layer 2: Manual Expert Testing (Catches ~50%)

What it finds:

  • Keyboard navigation issues
  • Focus management problems
  • Logical reading order failures
  • Meaningful alt text assessment
  • Cognitive accessibility barriers
  • Interaction pattern issues

Method:

  • Tab through every interactive element
  • Test with screen reader (VoiceOver or NVDA)
  • Test at 200% zoom
  • Test with system preferences enabled
  • Review content for plain language

When: before each release, on major feature changes Who: someone trained in accessibility testing

Layer 3: User Testing With Disabled People (Catches remaining ~20%)

What it finds:

  • Real-world usability barriers that experts miss
  • Assistive technology compatibility issues
  • Unexpected workflows and workarounds
  • Cognitive and emotional barriers
  • Issues that only appear with actual AT proficiency

Method:

  • Recruit participants with diverse disabilities
  • Test core tasks with their own devices and AT
  • Observe — don't guide or explain
  • Record what works, what fails, and what frustrates

When: quarterly, or before major launches Who: users with disabilities using their own setup

What to Test First

Priority 1: Core Tasks

  • Can users complete the primary tasks the product exists for?
  • Test the critical path end to end
  • Any failure here is a launch blocker

Read the full file on GitHub · 125 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. 2mo ago First seen · 125 lines · 87 tokens per session scan A 51f905302a67

Subscribe to this mod's changes

accessibility-testing-strategy is a skill published in the GitHub repository Owl-Listener/inclusive-design-skills (108 stars, last pushed 5mo ago), licensed MIT. It adds 87 tokens to every session and 883 once invoked, about $0.0003 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.

Design and UXTesting
Related

accessibility-testing-strategy compared with skills from other repositories

accessibility-testing-strategy next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
accessibility-testing-strategyOwl-Listener/inclusive-design-skillsSkill1085mo agoMITA87Claude Code
webgl-holographic-foilnexu-io/open-designSkill106kyesterdayApache-2.0A41Claude Code, Codex
html-ppt-hermes-cyber-terminalnexu-io/open-designSkill106kyesterdayApache-2.0A53Claude Code, Codex
html-ppt-taste-brutalistnexu-io/open-designSkill106kyesterdayApache-2.0A78Claude Code, Codex
visual-ralphYeachan-Heo/oh-my-codexSkill34k3d agoMITA52Codex
glance-canonical-layoutsandroid/skillsSkill10kyesterdayApache-2.0A56Claude Code
accessibilitymicrosoft/hve-coreSkill1.6kyesterdayMITA47Claude Code