iOS Accessibility Testing
conorluddy/xclaude-plugin
Guides WCAG 2.1 and VoiceOver accessibility testing for iOS apps, working from the accessibility tree and not from screenshots.
Plan what to test, how to test, and who should test for accessibility.
Install Accessibility Testing Strategy
$ npx skills add Owl-Listener/inclusive-design-skills --skill accessibility-testing-strategy -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills accessibility-testing-strategy --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/accessibility-decisions/skills/accessibility-testing-strategy .claude/skills/accessibility-testing-strategy && rm -rf skills-srcUse ~/.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/
Install the "accessibility-testing-strategy" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessibility-decisions/skills/accessibility-testing-strategy into .claude/skills/accessibility-testing-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "accessibility-testing-strategy", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessibility-decisions/skills/accessibility-testing-strategyType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Owl-Listener/inclusive-design-skills --skill accessibility-testing-strategy -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills accessibility-testing-strategy --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/accessibility-decisions/skills/accessibility-testing-strategy .agents/skills/accessibility-testing-strategy && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "accessibility-testing-strategy" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessibility-decisions/skills/accessibility-testing-strategy into .agents/skills/accessibility-testing-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "accessibility-testing-strategy", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/inclusive-design-skills --skill accessibility-testing-strategy -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills accessibility-testing-strategy --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/accessibility-decisions/skills/accessibility-testing-strategy .cursor/skills/accessibility-testing-strategy && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "accessibility-testing-strategy" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessibility-decisions/skills/accessibility-testing-strategy into .cursor/skills/accessibility-testing-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "accessibility-testing-strategy", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Owl-Listener/inclusive-design-skills.git --path accessibility-decisions/skills/accessibility-testing-strategy--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Owl-Listener/inclusive-design-skills --skill accessibility-testing-strategy -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills accessibility-testing-strategy --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/accessibility-decisions/skills/accessibility-testing-strategy .gemini/skills/accessibility-testing-strategy && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "accessibility-testing-strategy" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessibility-decisions/skills/accessibility-testing-strategy into .gemini/skills/accessibility-testing-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "accessibility-testing-strategy", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Owl-Listener/inclusive-design-skills accessibility-testing-strategyInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Owl-Listener/inclusive-design-skills --skill accessibility-testing-strategy -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/accessibility-decisions/skills/accessibility-testing-strategy .github/skills/accessibility-testing-strategy && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "accessibility-testing-strategy" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessibility-decisions/skills/accessibility-testing-strategy into .github/skills/accessibility-testing-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "accessibility-testing-strategy", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Owl-Listener/inclusive-design-skills --skill accessibility-testing-strategy -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Owl-Listener/inclusive-design-skills accessibility-testing-strategy --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Owl-Listener/inclusive-design-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/accessibility-decisions/skills/accessibility-testing-strategy .opencode/skills/accessibility-testing-strategy && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "accessibility-testing-strategy" agent skill from https://github.com/Owl-Listener/inclusive-design-skills/tree/main/accessibility-decisions/skills/accessibility-testing-strategy into .opencode/skills/accessibility-testing-strategy/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "accessibility-testing-strategy", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
accessibility-testing-strategy- GitHub stars
- 103
- Token cost
- ~1k tokens
- SKILL.md length
- 505 words
- Files
- 1
- Skills in repo
- 55
- Repo updated
- First seen
- Licence
- MIT
At a glance
Plan what to test, how to test, and who should test for accessibility.
- Works in 5 steps: Is automated testing running on every… → Is manual expert testing happening… → Has the product been tested by people… → …
- Defining a testing approach
- SKILL.md covers The Testing Pyramid, What to Test First, Screen Reader Testing Basics and Assessment Questions
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Accessibility Testing Strategy is an agent skill from Owl-Listener/inclusive-design-skills. Plan what to test, how to test, and who should test for accessibility. Use when defining a testing approach, planning QA, setting up automated and manual testing, or deciding what level of accessibility testing a project needs. Triggers on: accessibility testing, how to test, test plan, automated testing, manual testing, screen reader testing, user testing, accessibility QA, what to test, testing strategy.
Its SKILL.md is about 1k 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 Testing & QA, covering Accessibility. The repository describes itself as: Inclusive design skills for AI coding agents — from cognitive accessibility to adaptive interfaces, inclusive research, and accessibility decision-making. The licence is MIT.
When your agent uses it
- Defining a testing approach
- Setting up automated and manual testing
- Deciding what level of accessibility testing a project needs
- : accessibility testing
Example prompts
- “/accessibility-testing-strategy”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Is automated testing running on every build?
- Is manual expert testing happening before each release?
- Has the product been tested by people with disabilities?
- Are core tasks tested with keyboard and screen reader?
- Is there a clear priority for what to test first?
What it can do on your machine
Read from SKILL.md and the folder at commit 6e0740f. 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 Testing Strategy loads about 1k tokens when it runs. Until then it costs about 110 tokens; SKILL.md has 505 words of instructions outside code blocks.
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/inclusive-design-skills at commit 6e0740f, republished under its MIT licence (© Owl-Listener). 505 words, ~1,000 tokens.
Download SKILL.mdSave it as
.claude/skills/accessibility-testing-strategy/SKILL.md (or your agent's skills folder).- name
- accessibility-testing-strategy
- description
- Plan what to test, how to test, and who should test for accessibility. Use when defining a testing approach, planning QA, setting up automated and manual testing, or deciding what level of accessibility testing a project needs. Triggers on: accessibility testing, how to test, test plan, automated testing, manual testing, screen reader testing, user testing, accessibility QA, what to test, testing strategy.
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
Priority 2: Input and Navigation
- Keyboard-only navigation through the core flow
- Screen reader navigation through the core flow
- Touch interaction on mobile for the core flow
Show full SKILL.md (194 more words)Show less
Priority 3: Content and Comprehension
- Is content understandable at the target reading level?
- Are error messages helpful?
- Is help available and findable?
Priority 4: Edge Cases and Preferences
- Zoom to 200%
- System preferences (reduced motion, high contrast, dark mode)
- Long content, empty states, error states
Screen Reader Testing Basics
For teams new to screen reader testing:
Start With VoiceOver (Mac)
- Turn on: Cmd + F5
- Navigate: VO + arrow keys (VO = Ctrl + Option)
- Headings: VO + Cmd + H
- Links: VO + Cmd + L
- Forms: VO + Cmd + J
- Turn off: Cmd + F5
Start With NVDA (Windows)
- Download free from nvaccess.org
- Navigate: Tab, arrow keys
- Headings: H
- Links: K
- Forms: F
- Stop speech: Ctrl
What to Listen For
- Does every interactive element have a name?
- Are state changes announced (expanded, selected, checked)?
- Does focus move to the right place after actions?
- Can you understand the page reading only the headings?
Assessment Questions
- Is automated testing running on every build?
- Is manual expert testing happening before each release?
- Has the product been tested by people with disabilities?
- Are core tasks tested with keyboard and screen reader?
- Is there a clear priority for what to test first?
© 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 accessibility-decisions/skills/accessibility-testing-strategy of Owl-Listener/inclusive-design-skills.
Open the folder on GitHubat commit 6e0740f
Compare with similar skills
Accessibility Testing Strategy 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Accessibility Testing Strategy this skillOwl-Listener/inclusive-design-skills | 103 | — | ~1k | Automated safety check: Pass | MIT | |
| iOS Accessibility Testingconorluddy/xclaude-plugin | 183 | — | ~5k | Automated safety check: Pass | MIT | |
| Ds Test Componentbaloise/design-system | 114 | — | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Scoutqa Testgithub/awesome-copilot | 40k | 1 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Accessibility Testing LeadFerroxLabs/wayland | 608 | — | ~4.5k | Automated safety check: Pass | Apache-2.0 | |
| Test Scenariosborghei/Claude-Skills | 881 | — | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
Ds Test Component
baloise/design-system
Auto-generate all test files for DS components including visual, a11y, component, page object, and unit tests.
- Official
Scoutqa Test
github/awesome-copilot
This skill should be used when the user asks to "test this website", "run exploratory testing", "check for accessibility issues", "verify the login flow works", "find bugs on this page", or requests…
Accessibility Testing Lead
FerroxLabs/wayland
Design and execute comprehensive accessibility testing strategies combining automated scanning, manual evaluation, and assistive technology testing, with audit templates and stakeholder reporting.
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.
Kb Testing Strategy
Community-Access/accessibility-agents
Reference data, not a reviewer. An agent skill from Community-Access/accessibility-agents.
More from Owl-Listener/inclusive-design-skills
All 55 skills in this repoAssistive Technology Scenarios
Owl-Listener/inclusive-design-skills
Writes usage scenarios, use cases and storyboards that show real people using screen readers, switches, voice control and other assistive technology to finish tasks.
Error Prevention and Recovery
Owl-Listener/inclusive-design-skills
Designs forgiving forms and flows: prevent input errors, write messages that say what happened and what to do, and add undo, confirmation and recovery paths.
Accessible Heading Structure
Owl-Listener/inclusive-design-skills
Designs heading hierarchies for screen reader navigation and cognitive accessibility on pages, articles, dashboards and forms.
Ability Spectrum Mapping
Owl-Listener/inclusive-design-skills
Maps a feature across a range of vision, hearing, motor and cognitive ability to find where the design starts to fail, and to explain accessibility scope to stakeholders.
Accessibility Debt Tracking
Owl-Listener/inclusive-design-skills
Track and manage accessibility debt — known accessibility issues that have been deferred.
Alt Text Design
Owl-Listener/inclusive-design-skills
Write meaningful alternative text for images, charts, diagrams, and visual content.
Related
Categories
Questions about Accessibility Testing Strategy
What does Accessibility Testing Strategy do?
Plan what to test, how to test, and who should test for accessibility. Accessibility Testing Strategy is an agent skill from Owl-Listener/inclusive-design-skills. Plan what to test, how to test, and who should test for accessibility.
When should I use Accessibility Testing Strategy?
Accessibility Testing Strategy fits situations like: defining a testing approach; setting up automated and manual testing; deciding what level of accessibility testing a project needs; : accessibility testing.
How do I install Accessibility Testing Strategy in Claude Code?
Run `npx skills add Owl-Listener/inclusive-design-skills --skill accessibility-testing-strategy -a claude-code`. Or copy the skill folder (accessibility-decisions/skills/accessibility-testing-strategy in Owl-Listener/inclusive-design-skills) into .claude/skills/accessibility-testing-strategy in your project. Claude Code loads it when a task matches its description.
How do I install Accessibility Testing Strategy in Codex?
Run `npx skills add Owl-Listener/inclusive-design-skills --skill accessibility-testing-strategy -a codex`. Or copy the skill folder (accessibility-decisions/skills/accessibility-testing-strategy in Owl-Listener/inclusive-design-skills) into .agents/skills/accessibility-testing-strategy in your project. Codex loads it when a task matches its description.
Can I use Accessibility Testing Strategy 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/inclusive-design-skills --skill accessibility-testing-strategy -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-testing-strategy, .gemini/skills/accessibility-testing-strategy, .github/skills/accessibility-testing-strategy and .opencode/skills/accessibility-testing-strategy in your project.
What does Accessibility Testing Strategy need to run?
SKILL.md names no scripts, command-line tools or credentials: Accessibility Testing Strategy is instructions for the agent only.
Does Accessibility Testing Strategy 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 Testing Strategy 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 Testing Strategy use?
Accessibility Testing Strategy 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 Testing Strategy use?
About 1k tokens (SKILL.md is roughly 4k 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 Testing Strategy?
Skills that share tags, products or a category with Accessibility Testing Strategy: iOS Accessibility Testing (conorluddy/xclaude-plugin, 183 stars), Ds Test Component (baloise/design-system, 114 stars), Scoutqa Test (github/awesome-copilot, 40k stars) and Accessibility Testing Lead (FerroxLabs/wayland, 608 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Accessibility Testing Strategy?
Owl-Listener (a GitHub user) maintains it in Owl-Listener/inclusive-design-skills, which has 103 GitHub stars. The repository holds 55 skills in this directory. The repository was last updated on June 9, 2026.
Source: Owl-Listener/inclusive-design-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.