qe-accessibility-testing
This skill provides automated accessibility validation aligned with WCAG 2.2 standards, helping teams systematically verify compliance and meet regulatory obligations. Built for quality engineering workflows, it integrates accessibility checks into your testing pipeline to catch barriers early and ensure your applications remain accessible to all users.
qe-accessibility-testing delivers automated accessibility validation aligned with WCAG 2.2 standards, enabling teams to systematically verify compliance and meet regulatory obligations. The skill integrates comprehensive checks into your quality engineering workflows to catch accessibility barriers early and ensure your applications remain accessible to all users, supporting both legal requirements and inclusive design principles.
AI-generated summary based on this skill's SKILL.md
Install
proffesor-for-testing/agentic-qe/qe-accessibility-testing · repository language: TypeScript
git clone https://github.com/proffesor-for-testing/agentic-qe
cp -r agentic-qe/.kiro/skills/qe-accessibility-testing ~/.claude/skills/qe-accessibility-testingFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
What WCAG 2.2 compliance testing capabilities does qe-accessibility-testing provide?
qe-accessibility-testing delivers automated accessibility validation aligned with WCAG 2.2 standards, enabling teams to systematically verify compliance and meet regulatory obligations. The skill integrates comprehensive checks into your quality engineering workflows to catch accessibility barriers early and ensure your applications remain accessible to all users, supporting both legal requirements and inclusive design principles.
Can qe-accessibility-testing test screen reader compatibility with assistive technologies?
Yes, qe-accessibility-testing is built to test keyboard navigation and screen reader compatibility with assistive technologies. This includes validation across tools like VoiceOver, NVDA, and JAWS, ensuring that your interactive elements work correctly for users relying on screen readers and other assistive devices to navigate your application.
How does qe-accessibility-testing automate accessibility testing in CI/CD pipelines?
qe-accessibility-testing integrates accessibility checks directly into your CI/CD pipeline, allowing you to automate a11y testing and catch violations early in the development cycle. By embedding these automated checks into your continuous integration workflow, you prevent accessibility issues from reaching production and maintain consistent compliance throughout your release process.
What specific accessibility elements does qe-accessibility-testing validate?
qe-accessibility-testing validates color contrast, focus indicators, and form accessibility requirements across all interactive elements. It performs inclusive design verification to ensure users with disabilities can access and interact with your application, including checks for alt text, form labels, and other critical accessibility components aligned with WCAG 2.2 and Section 508 compliance standards.
Is qe-accessibility-testing suitable for ADA accessibility audits and regulatory compliance?
Yes, qe-accessibility-testing is designed to support ADA accessibility audits and meet regulatory compliance requirements. The skill provides systematic validation of accessibility standards and POUR principles testing, helping your organization demonstrate compliance with legal obligations and accessibility regulations while ensuring your digital products are truly accessible to all users.
What license does qe-accessibility-testing use?
qe-accessibility-testing is released under the MIT license, making it freely available for use, modification, and distribution in both open-source and commercial projects with minimal restrictions.
SKILL.md
rendered from the published skill — quoted content, verbatim
Accessibility Testing
<default_to_action> When testing accessibility or ensuring compliance: 1. APPLY POUR principles: Perceivable, Operable, Understandable, Robust 2. TEST with keyboard-only navigation (Tab, Enter, Escape) 3. VALIDATE with screen readers (VoiceOver, NVDA, JAWS) 4. CHECK color contrast (4.5:1 for text, 3:1 for large text) 5. AUTOMATE with axe-core, integrate in CI/CD pipeline
Quick A11y Checklist: - All images have alt text (or alt="" for decorative) - All form fields have labels - Color is never the only indicator - Focus visible on all interactive elements - Keyboard navigation works throughout
Critical Success Factors: - Automated testing catches 30-50% of issues - Manual testing with real assistive tech required - Include users with disabilities in
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
.kiro/skills/qe-accessibility-testing/SKILL.md