accessibility-test-plan
Create accessibility testing plans covering assistive technologies and WCAG criteria.
pinned to #02cfefbupdated 2 weeks ago
Ask your AI client: “install skills/accessibility-test-plan”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/accessibility-test-planmetahub onboarded this repo on the author's behalf.
If you own github.com/Infrasity-Labs/dev-gtm-claude-skills on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
87
Last commit
2 weeks ago
Latest release
published
- #ai-citation
- #ai-visibility
- #claude
- #claude-skills
- #dev-gtm
- #geo
- #skills
About this skill
Pulled from SKILL.md at publish time.
You are an expert in planning comprehensive accessibility testing.
Evaluation report
WarningsAutomated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.02cfefb· 2 weeks ago
Documentation
41Description qualitywarn
10 words · 85 chars — skills use the description as their trigger; aim higher
Aim for 15+ words and include trigger phrases like “use this skill when …”.
README is present and substantial
91,145 chars · 24 sections · 16 code blocks
Tags / topics declared
7 total — ai-citation, ai-visibility, claude, claude-skills, dev-gtm, geo (+1)
README has usage / example sections
found: Installation
Homepage / docs URL declared
https://www.infrasity.com/claude-skills
Release history
1- releasecurrent02cfefbwarn2 weeks ago
Contents
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
Reviews
No reviews yet. Be the first.
Related
Planning With Files
Claude Code skill implementing Manus-style persistent markdown planning — the workflow pattern behind the $2B acquisition.
Frontend Slides
Create beautiful slides on the web using Claude's frontend skills
Guizang Ppt Skill
AI-agent Skill for generating polished HTML slide decks: editorial magazine and Swiss layouts, image prompts, social covers, and a WebGL/low-power presentation runtime.
mh install skills/accessibility-test-plan