How do I install the Accessibility Testing skill?

Run npx skillmds@latest add ashutoshsrivastava17/accessibility-testing in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Accessibility Testing safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Accessibility Testing?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Accessibility Testing free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Accessibility Testing?

ashutoshsrivastava17 (@ashutoshsrivastava17) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Accessibility Testing by ashutoshsrivastava17

Name: Accessibility Testing
Author: ashutoshsrivastava17

Accessibility Testing

Plan accessibility testing — WCAG 2.1 criteria, screen reader testing, keyboard navigation, color contrast, and assistive technology coverage. TRIGGER when: user says /accessibility-testing, needs to test for accessibility, or asks about WCAG compliance testing.

File contents

Accessibility Testing Plan

Process

Step 1: Define WCAG Compliance Target

Level	Criteria	Typical Requirement
A	Basic accessibility	Minimum legal compliance
AA	Standard accessibility	Most common requirement
AAA	Enhanced accessibility	Best practice, not usually required

Step 2: Automated Testing

Tool	What It Catches
axe / Lighthouse	Color contrast, missing alt text, ARIA issues
WAVE	Structural issues, reading order
Pa11y	CI/CD integration, regression checking

Step 3: Manual Testing

Test	Method	WCAG Criteria
Keyboard navigation	Tab through all interactive elements	2.1.1
Focus visibility	Verify focus indicators visible	2.4.7
Screen reader	Test with NVDA/JAWS/VoiceOver	1.3.1, 4.1.2
Color contrast	4.5:1 for text, 3:1 for large text	1.4.3
Zoom	Content usable at 200% zoom	1.4.4
Motion	Animations respect prefers-reduced-motion	2.3.3
Form labels	All inputs have associated labels	1.3.1
Error identification	Errors are clearly described	3.3.1

Step 4: Assistive Technology Matrix

AT	OS	Browser	Priority
VoiceOver	macOS	Safari	High
NVDA	Windows	Chrome/Firefox	High
JAWS	Windows	Chrome	Medium
TalkBack	Android	Chrome	Medium

Step 5: Report Findings

Issue	WCAG	Severity	Element	Recommendation
[issue]	[criteria]	H/M/L	[selector]	[fix]

Output Format

## Accessibility Report: [Application]
### Compliance Target: WCAG [level]
### Automated: [X issues found]
### Manual: [Findings by category]
### AT Testing: [Screen reader results]
### Recommendations: [Prioritized fixes]

Quality Checklist

Both automated and manual testing performed
Screen reader testing with at least 2 AT combinations
Keyboard navigation fully tested
Color contrast verified
Findings mapped to WCAG criteria

Edge Cases

For SPAs, test dynamic content and route changes with screen readers
For data visualizations, ensure alternative text descriptions
For video content, verify captions and audio descriptions

---name: accessibility-testingdescription: Plan accessibility testing — WCAG 2.1 criteria, screen reader testing, keyboard navigation, color contrast, and assistive technology coverage. TRIGGER when: user says /accessibility-testing, needs to test for accessibility, or asks about WCAG compliance testing.---# Accessibility Testing Plan## Process### Step 1: Define WCAG Compliance Target| Level | Criteria | Typical Requirement ||-------|---------|-------------------|| A | Basic accessibility | Minimum legal compliance || AA | Standard accessibility | Most common requirement || AAA | Enhanced accessibility | Best practice, not usually required |### Step 2: Automated Testing| Tool | What It Catches ||------|----------------|| axe / Lighthouse | Color contrast, missing alt text, ARIA issues || WAVE | Structural issues, reading order || Pa11y | CI/CD integration, regression checking |### Step 3: Manual Testing| Test | Method | WCAG Criteria ||------|--------|-------------|| Keyboard navigation | Tab through all interactive elements | 2.1.1 || Focus visibility | Verify focus indicators visible | 2.4.7 || Screen reader | Test with NVDA/JAWS/VoiceOver | 1.3.1, 4.1.2 || Color contrast | 4.5:1 for text, 3:1 for large text | 1.4.3 || Zoom | Content usable at 200% zoom | 1.4.4 || Motion | Animations respect prefers-reduced-motion | 2.3.3 || Form labels | All inputs have associated labels | 1.3.1 || Error identification | Errors are clearly described | 3.3.1 |### Step 4: Assistive Technology Matrix| AT | OS | Browser | Priority ||----|-----|---------|----------|| VoiceOver | macOS | Safari | High || NVDA | Windows | Chrome/Firefox | High || JAWS | Windows | Chrome | Medium || TalkBack | Android | Chrome | Medium |### Step 5: Report Findings| Issue | WCAG | Severity | Element | Recommendation ||-------|------|----------|---------|---------------|| [issue] | [criteria] | H/M/L | [selector] | [fix] |## Output Format```markdown## Accessibility Report: [Application]### Compliance Target: WCAG [level]### Automated: [X issues found]### Manual: [Findings by category]### AT Testing: [Screen reader results]### Recommendations: [Prioritized fixes]```## Quality Checklist- [ ] Both automated and manual testing performed- [ ] Screen reader testing with at least 2 AT combinations- [ ] Keyboard navigation fully tested- [ ] Color contrast verified- [ ] Findings mapped to WCAG criteria## Edge Cases- For SPAs, test dynamic content and route changes with screen readers- For data visualizations, ensure alternative text descriptions- For video content, verify captions and audio descriptions

Frequently asked questions