Agent skill

Accessibility Test Plan

by Owl-Listener in Owl-Listener/designer-skills

Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol.

MITAuto-check passedFrontend & Design

Install Accessibility Test Plan

skills CLI
$ npx skills add Owl-Listener/designer-skills --skill accessibility-test-plan -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Owl-Listener/designer-skills accessibility-test-plan --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/prototyping-testing/skills/accessibility-test-plan .claude/skills/accessibility-test-plan && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
accessibility-test-plan
GitHub stars
2.9k
Used in
1 other repo
Token cost
~478 tokens
SKILL.md length
208 words
Files
1
Skills in repo
107
Repo updated
First seen
Licence
MIT

At a glance

Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol.

  • Works in 4 steps: Automated Testing → Manual Testing → Assistive Technology Testing → …
  • Scheduling testing with real AT users
  • SKILL.md covers What You Do, Testing Layers, Test Matrix and WCAG Criteria Checklist, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Accessibility Test Plan is an agent skill from Owl-Listener/designer-skills. Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use accessibility-audit (design-systems).

Its SKILL.md is about 480 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design, covering Accessibility and Test generation. The repository describes itself as: Designer Skills Collection: agentic skills, commands, and plugins for design — from research to systems, UI, interaction, and delivery. The licence is MIT.

When your agent uses it

  • Scheduling testing with real AT users
  • Tasks that involve Accessibility
  • Tasks that involve Test generation

Example prompts

  • “/accessibility-test-plan”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Automated Testing
  2. Manual Testing
  3. Assistive Technology Testing
  4. User Testing with Disabilities

What it can do on your machine

Read from SKILL.md and the folder at commit 9a6930c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Accessibility Test Plan loads about 478 tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 208 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~67
When it runs · the whole SKILL.md, loaded when a task matches
~478

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Owl-Listener/designer-skills at commit 9a6930c, republished under its MIT licence (© Owl-Listener). 208 words, ~478 tokens.

Download SKILL.mdSave it as .claude/skills/accessibility-test-plan/SKILL.md (or your agent's skills folder).
name
accessibility-test-plan
description
Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).

Accessibility Test Plan

You are an expert in planning comprehensive accessibility testing.

What You Do

You create testing plans that systematically evaluate accessibility across assistive technologies and WCAG criteria.

Testing Layers

1. Automated Testing
  • Axe, Lighthouse, WAVE tools
  • Catches approximately 30-40% of issues
  • Run on every page/state
  • Integrate into CI/CD pipeline
2. Manual Testing
  • Keyboard-only navigation
  • Screen reader walkthrough
  • Zoom to 200% and 400%
  • High contrast mode
  • Reduced motion mode
3. Assistive Technology Testing
  • Screen readers: VoiceOver (Mac/iOS), NVDA (Windows), TalkBack (Android)
  • Voice control: Voice Control (Mac/iOS), Dragon
  • Switch control
  • Screen magnification
4. User Testing with Disabilities
  • Recruit participants with relevant disabilities
  • Include variety (vision, motor, cognitive, hearing)
  • Test with their own devices and settings
  • Focus on real tasks, not compliance checkboxes

Test Matrix

For each key user flow, test across: keyboard only, VoiceOver, NVDA, zoom 200%, high contrast, reduced motion.

WCAG Criteria Checklist

Organize by principle (Perceivable, Operable, Understandable, Robust) and level (A, AA, AAA).

Reporting

For each issue: description, WCAG criterion, severity, assistive tech affected, steps to reproduce, remediation.

Best Practices

  • Test early and continuously, not just before launch
  • Automated testing is necessary but not sufficient
  • Test with real assistive technology users
  • Include accessibility in definition of done
  • Prioritize by user impact, not just compliance level

© Owl-Listener, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in prototyping-testing/skills/accessibility-test-plan of Owl-Listener/designer-skills.

Open the folder on GitHubat commit 9a6930c

Used in 1 other repository

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in Owl-Listener/designer-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Accessibility Test Plan next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Accessibility Test Plan compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Accessibility Test Plan this skillOwl-Listener/designer-skills2.9k1 repos~478Automated safety check: PassMIT
Test Scenariosborghei/Claude-Skills881—~1.9kAutomated safety check: PassMIT
Corgispec QA UIricoyudog/Coding_Corgi_flow104—~1.5kAutomated safety check: PassMIT
Web Interface Guidelines Reviewervercel-labs/openreview1.7k98 repos~308Automated safety check: PassNone
Accessibility Reviewmarkmead/hyperui12k1 repos~1.1kAutomated safety check: PassMIT
Web Animation DesignbaptisteArno/typebot.io11k2 repos~2.7kAutomated safety check: PassCustom licence

Similar skills

  • Test Scenarios

    borghei/Claude-Skills

    Generate test scenario coverage from a feature spec — happy paths, edge cases, error handling, accessibility, security, and performance — with a coverage analyzer that flags gaps.

    881 GitHub stars~1.9k tokensUpdated yesterday
    Testing & QAAuto-check passed
  • Corgispec QA UI

    ricoyudog/Coding_Corgi_flow

    UI walkthrough — real user path verification with screenshots, component state checks, keyboard navigation, and cross-browser testing

    104 GitHub stars~1.5k tokensUpdated 1 mo ago
    Testing & QAAuto-check passed
  • Web Interface Guidelines Reviewer

    vercel-labs/openreview

    Official

    Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…

    1.7k GitHub starsUsed in 98 repos~308 tokens
    Frontend & DesignAuto-check passed
  • Accessibility Review

    markmead/hyperui

    Run a WCAG 2.1 AA accessibility audit on a design or page. An agent skill from markmead/hyperui.

    12k GitHub starsUsed in 1 repo~1.1k tokens
    Frontend & DesignAuto-check passed
  • Web Animation Design

    baptisteArno/typebot.io

    Guides easing, timing and animation choices for UI motion, based on a web animation course, and reviews existing animations in a before-and-after table.

    11k GitHub starsUsed in 2 repos~2.7k tokens
    Frontend & DesignAuto-check passed
  • Accessibility Fixer

    ibelick/ui-skills

    Audits and fixes HTML accessibility problems such as ARIA labels, keyboard navigation, focus management, contrast and form errors with minimal changes.

    9.5k GitHub starsUsed in 4 repos~1.2k tokens
    Frontend & DesignAuto-check passed

More from Owl-Listener/designer-skills

All 107 skills in this repo
  • A B Test Design

    Owl-Listener/designer-skills

    Design an A/B experiment — hypothesis, variants, primary metric, and sample size.

    2.9k GitHub starsUsed in 1 repo~472 tokens
    Auto-check passed
  • Aesthetic Usability

    Owl-Listener/designer-skills

    Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction.

    2.9k GitHub starsUsed in 1 repo~678 tokens
    Auto-check passed
  • Affinity Diagram

    Owl-Listener/designer-skills

    Cluster many qualitative data points into themes and insight statements.

    2.9k GitHub starsUsed in 1 repo~520 tokens
    Auto-check passed
  • Animation Principles

    Owl-Listener/designer-skills

    Apply animation principles — easing, staging, follow-through — to one specific UI motion.

    2.9k GitHub starsUsed in 1 repo~492 tokens
    Auto-check passed
  • Business Design

    Owl-Listener/designer-skills

    Read financials, map competitive landscapes, and argue design decisions in the language of value.

    2.9k GitHub starsUsed in 1 repo~1.1k tokens
    Auto-check passed
  • Case Study

    Owl-Listener/designer-skills

    Craft a portfolio case study with narrative arc, process evidence, and outcomes.

    2.9k GitHub starsUsed in 1 repo~523 tokens
    Auto-check passed

Questions about Accessibility Test Plan

What does Accessibility Test Plan do?

Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Accessibility Test Plan is an agent skill from Owl-Listener/designer-skills. Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol.

When should I use Accessibility Test Plan?

Accessibility Test Plan fits situations like: scheduling testing with real AT users; tasks that involve Accessibility; tasks that involve Test generation.

How do I install Accessibility Test Plan in Claude Code?

Run `npx skills add Owl-Listener/designer-skills --skill accessibility-test-plan -a claude-code`. Or copy the skill folder (prototyping-testing/skills/accessibility-test-plan in Owl-Listener/designer-skills) into .claude/skills/accessibility-test-plan in your project. Claude Code loads it when a task matches its description.

How do I install Accessibility Test Plan in Codex?

Run `npx skills add Owl-Listener/designer-skills --skill accessibility-test-plan -a codex`. Or copy the skill folder (prototyping-testing/skills/accessibility-test-plan in Owl-Listener/designer-skills) into .agents/skills/accessibility-test-plan in your project. Codex loads it when a task matches its description.

Can I use Accessibility Test Plan in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Owl-Listener/designer-skills --skill accessibility-test-plan -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/accessibility-test-plan, .gemini/skills/accessibility-test-plan, .github/skills/accessibility-test-plan and .opencode/skills/accessibility-test-plan in your project.

What does Accessibility Test Plan need to run?

SKILL.md names no scripts, command-line tools or credentials: Accessibility Test Plan is instructions for the agent only.

Does Accessibility Test Plan access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Accessibility Test Plan safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Accessibility Test Plan use?

Accessibility Test Plan is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Accessibility Test Plan use?

About 478 tokens (SKILL.md is roughly 1.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Accessibility Test Plan?

Skills that share tags, products or a category with Accessibility Test Plan: Test Scenarios (borghei/Claude-Skills, 881 stars), Corgispec QA UI (ricoyudog/Coding_Corgi_flow, 104 stars), Web Interface Guidelines Reviewer (vercel-labs/openreview, 1.7k stars) and Accessibility Review (markmead/hyperui, 12k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Accessibility Test Plan?

Owl-Listener (a GitHub user) maintains it in Owl-Listener/designer-skills, which has 2,854 GitHub stars. The repository holds 107 skills in this directory. The repository was last updated on September 5, 2026.

Source: Owl-Listener/designer-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.