- Home
- Skills
- 404kidwiz
- Claude Supercode Skills
- Accessibility Tester Skill
accessibility-tester-skill_skill
- Python
21
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill 404kidwiz/claude-supercode-skills --skill accessibility-tester-skill- SKILL.md13.8 KB
Overview
This skill is a WCAG 2.2 AA compliance expert focused on audits, automated testing, screen reader validation, and remediation guidance. It helps teams identify, prioritize, and fix accessibility barriers across web and mobile products. The skill delivers actionable reports, remediation scripts, and compliance documentation to support legal and usability goals.
How this skill works
I combine automated scanning (Axe, Pa11y, Lighthouse) with manual techniques: keyboard audits, screen reader checks (NVDA, VoiceOver, JAWS, TalkBack), and mobile touch/gesture validation. Results are triaged using a remediation prioritization matrix that maps impact and effort to clear fix priorities. I can generate VPATs, integrate tests into CI/CD, and provide code-level fixes and re-test validation.
When to use it
- Before launch to validate WCAG 2.1/2.2 AA compliance
- When adding components or a design system to ensure accessible primitives
- To integrate accessibility checks into CI/CD and prevent regressions
- When diagnosing keyboard, focus, or screen reader issues in production flows
- For mobile apps to verify touch target size, gestures, and dynamic type support
Best practices
- Automate early and run manual audits regularly; automated tools catch ~30–50% of issues
- Prefer semantic HTML and native controls over ARIA shims
- Prioritize fixes by impact (keyboard access, missing labels, contrast) before cosmetic adjustments
- Include people with disabilities in usability testing when possible
- Document evidence, track accessibility debt, and update VPATs when changes occur
Example use cases
- E-commerce launch: full automated + manual audit across product listing and checkout, plus remediation plan for missing alt text and focus traps
- Component library: unit tests with jest-axe, visual focus-state review, and screen reader expectations for each widget
- CI/CD pipeline: run Axe/Pa11y on critical paths, fail builds for high-severity violations, and auto-file issues for tracking
- Mobile app: touch target size audit, gesture alternatives review, and dynamic type scaling verification
FAQ
Test at minimum NVDA on Windows with Chrome/Firefox and VoiceOver on macOS/iOS with Safari; add JAWS and TalkBack for broader coverage.
Can automated tools guarantee compliance?
No. Automated tools find many issues quickly, but manual keyboard, screen reader, and mobile checks are required to reach WCAG AA compliance.