Use this agent when you need comprehensive accessibility testing, WCAG compliance verification, or assessment of assistive technology support. Specifically:\\n\\n<example>\\nContext: A web application is preparing for launch and needs to ensure compliance with accessibility standards before release.\\nuser: \"Can you test our web app for accessibility issues? We need to know if it works with screen readers and keyboard navigation, and if we meet WCAG standards.\"\\nassistant: \"I'll conduct a comprehensive accessibility audit covering WCAG 2.1 Level AA compliance, screen reader compatibility (NVDA, JAWS, VoiceOver), full keyboard navigation testing, color contrast verification, focus management, and ARIA implementation. I'll identify violations, prioritize by severity, and provide specific remediation guidance.\"\\n<commentary>\\nInvoke accessibility-tester when an application needs formal accessibility testing and compliance verification. This agent conducts systematic testing across multiple accessibility dimensions, unlike qa-expert which focuses on general quality assurance.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: Users with disabilities reported difficulty using the mobile app, and the team wants to understand and fix accessibility barriers.\\nuser: \"We're getting feedback that disabled users can't use our mobile app properly. Some can't navigate with the keyboard and others have trouble with the screen reader. What's wrong?\"\\nassistant: \"I'll test your mobile app with assistive technologies to identify specific accessibility barriers. I'll check touch target sizing, gesture alternatives, screen reader compatibility, keyboard navigation logic, and platform-specific accessibility features. I'll document each barrier with a clear explanation of the impact on users and concrete fixes needed.\"\\n<commentary>\\nUse accessibility-tester to diagnose accessibility problems reported by users and design solutions. This agent traces user complaints to specific accessibility failures and recommends fixes.\\n</commentary>\\n</example>\\n\\n<example>\\nContext: A development team has built a complex form with dynamic validation and wants to ensure it's accessible before merging the feature.\\nuser: \"We built a new checkout form with real-time validation. Can you check if it's accessible? We want to make sure errors are announced properly and the keyboard flow works.\"\\nassistant: \"I'll review the form's accessibility including label associations, error identification and announcement, field instructions, focus management during validation, keyboard navigation flow, and screen reader announcements. I'll identify any ARIA violations, test with actual assistive technologies, and verify the form meets WCAG standards.\"\\n<commentary>\\nInvoke accessibility-tester for component or feature-level accessibility validation before integration. This agent verifies specific UI patterns work correctly with assistive technology, catching issues before they reach users.\\n</commentary>\\n</example>
Score
Unranked
Evidence
No signals yet
Last commit
Not known
Listed
Install
$armory install accessibility-tester-2--cli claude
writes the file to.claude/agents/accessibility-tester-2.md·Listed as compatible
Configuration
# fetches the source and writes it to:
.claude/agents/accessibility-tester-2.md
Needs the armory CLI · not on npm yet, build it from cli/ in the repository
What it is
Use this agent when you need comprehensive accessibility testing, WCAG compliance verification, or assessment of assistive technology support. Specifically:\n\n\nContext: A web application is preparing for launch and needs to ensure compliance with accessibility standards before release.\nuser: "Can you test our web app for accessibility issues? We need to know if it works with screen readers and keyboard navigation, and if we meet WCAG standards."\nassistant: "I'll conduct a comprehensive accessibility audit covering WCAG 2.1 Level AA compliance, screen reader compatibility (NVDA, JAWS, VoiceOver), full keyboard navigation testing, color contrast verification, focus management, and ARIA implementation. I'll identify violations, prioritize by severity, and provide specific remediation guidance."\n\nInvoke accessibility-tester when an application needs formal accessibility testing and compliance verification. This agent conducts systematic testing across multiple accessibility dimensions, unlike qa-expert which focuses on general quality assurance.\n\n\n\n\nContext: Users with disabilities reported difficulty using the mobile app, and the team wants to understand and fix accessibility barriers.\nuser: "We're getting feedback that disabled users can't use our mobile app properly. Some can't navigate with the keyboard and others have trouble with the screen reader. What's wrong?"\nassistant: "I'll test your mobile app with assistive technologies to identify specific accessibility barriers. I'll check touch target sizing, gesture alternatives, screen reader compatibility, keyboard navigation logic, and platform-specific accessibility features. I'll document each barrier with a clear explanation of the impact on users and concrete fixes needed."\n\nUse accessibility-tester to diagnose accessibility problems reported by users and design solutions. This agent traces user complaints to specific accessibility failures and recommends fixes.\n\n\n\n\nContext: A development team has built a complex form with dynamic validation and wants to ensure it's accessible before merging the feature.\nuser: "We built a new checkout form with real-time validation. Can you check if it's accessible? We want to make sure errors are announced properly and the keyboard flow works."\nassistant: "I'll review the form's accessibility including label associations, error identification and announcement, field instructions, focus management during validation, keyboard navigation flow, and screen reader announcements. I'll identify any ARIA violations, test with actual assistive technologies, and verify the form meets WCAG standards."\n\nInvoke accessibility-tester for component or feature-level accessibility validation before integration. This agent verifies specific UI patterns work correctly with assistive technology, catching issues before they reach users.\n\n
When to use it
Use this agent when you need comprehensive accessibility testing, WCAG compliance verification, or assessment of assistive technology support. Specifically:\n\n\nContext: A web application is preparing for launch and needs to ensure compliance with accessibility standards before release.\nuser: "Can you test our web app for accessibility issues? We need to know if it works with screen readers and keyboard navigation, and if we meet WCAG standards."\nassistant: "I'll conduct a comprehensive accessibility audit covering WCAG 2.1 Level AA compliance, screen reader compatibility (NVDA, JAWS, VoiceOver), full keyboard navigation testing, color contrast verification, focus management, and ARIA implementation. I'll identify violations, prioritize by severity, and provide specific remediation guidance."\n\nInvoke accessibility-tester when an application needs formal accessibility testing and compliance verification. This agent conducts systematic testing across multiple accessibility dimensions, unlike qa-expert which focuses on general quality assurance.\n\n\n\n\nContext: Users with disabilities reported difficulty using the mobile app, and the team wants to understand and fix accessibility barriers.\nuser: "We're getting feedback that disabled users can't use our mobile app properly. Some can't navigate with the keyboard and others have trouble with the screen reader. What's wrong?"\nassistant: "I'll test your mobile app with assistive technologies to identify specific accessibility barriers. I'll check touch target sizing, gesture alternatives, screen reader compatibility, keyboard navigation logic, and platform-specific accessibility features. I'll document each barrier with a clear explanation of the impact on users and concrete fixes needed."\n\nUse accessibility-tester to diagnose accessibility problems reported by users and design solutions. This agent traces user complaints to specific accessibility failures and recommends fixes.\n\n\n\n\nContext: A development team has built a complex form with dynamic validation and wants to ensure it's accessible before merging the feature.\nuser: "We built a new checkout form with real-time validation. Can you check if it's accessible? We want to make sure errors are announced properly and the keyboard flow works."\nassistant: "I'll review the form's accessibility including label associations, error identification and announcement, field instructions, focus management during validation, keyboard navigation flow, and screen reader announcements. I'll identify any ARIA violations, test with actual assistive technologies, and verify the form meets WCAG standards."\n\nInvoke accessibility-tester for component or feature-level accessibility validation before integration. This agent verifies specific UI patterns work correctly with assistive technology, catching issues before they reach users.\n\n
How to install / invoke
# Copy the agent definition into your project's .claude/agents/
curl -sL https://raw.githubusercontent.com/davila7/claude-code-templates/main/cli-tool/components/agents/development-tools/accessibility-tester.md -o .claude/agents/accessibility-tester.md