accessibility-selenium-testing
This skill equips QA engineers with practical patterns to integrate accessibility compliance checks into Selenium-based test automation workflows. Detect WCAG 2.1 and 2.2 violations programmatically, catching accessibility regressions before production. Built tool-agnostic for use with Copilot, Claude, Cursor, and other AI agents.
accessibility-selenium-testing equips QA engineers with practical patterns to integrate WCAG 2.1 and 2.2 compliance checks directly into Selenium test automation workflows. The skill enables automated scanning for accessibility violations, allowing teams to detect regressions before production and enforce compliance gates in CI/CD pipelines. It works tool-agnostic across Copilot, Claude, Cursor, and other AI agents.
AI-generated summary based on this skill's SKILL.md
Install
fugazi/test-automation-skills-agents/accessibility-selenium-testing · repository language: Java
git clone https://github.com/fugazi/test-automation-skills-agents
cp -r test-automation-skills-agents/skills/accessibility-selenium-testing ~/.claude/skills/accessibility-selenium-testingFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How does accessibility-selenium-testing help with selenium accessibility testing wcag compliance?
accessibility-selenium-testing equips QA engineers with practical patterns to integrate WCAG 2.1 and 2.2 compliance checks directly into Selenium test automation workflows. The skill enables automated scanning for accessibility violations, allowing teams to detect regressions before production and enforce compliance gates in CI/CD pipelines. It works tool-agnostic across Copilot, Claude, Cursor, and other AI agents.
Can accessibility-selenium-testing test keyboard navigation and focus order programmatically?
Yes. accessibility-selenium-testing provides patterns to test keyboard navigation, focus order, and screen reader compatibility programmatically within Selenium tests. The skill covers keyboard trap detection, focus order validation, and ARIA semantics auditing, enabling comprehensive keyboard accessibility verification as part of automated test suites.
What violations does accessibility-selenium-testing detect in automated scans?
accessibility-selenium-testing detects WCAG 2.1 and 2.2 violations across all POUR principles—Perceivable, Operable, Understandable, and Robust. Specific audits include color contrast failures, ARIA semantics errors, keyboard navigation issues, screen reader incompatibilities, and semantic HTML violations. Violations are categorized by impact level and rule category for triage.
How can accessibility-selenium-testing integrate accessibility testing into CI/CD pipelines?
accessibility-selenium-testing enables teams to embed accessibility compliance checks as pass/fail gates in CI/CD pipelines. The skill provides patterns for automated violation detection, detailed accessibility report generation, and impact-level triage, allowing critical violations to block deployments and non-critical issues to be logged for remediation tracking.
What component-level audits does accessibility-selenium-testing support?
accessibility-selenium-testing supports auditing specific components or pages for ARIA semantics, color contrast compliance, keyboard accessibility, focus management, and POUR principle adherence. The skill enables granular, component-focused scans rather than full-page audits, making it practical for testing individual UI elements within larger Selenium test suites.
Does accessibility-selenium-testing generate detailed accessibility reports?
Yes. accessibility-selenium-testing generates detailed accessibility reports that categorize violations by impact level and rule category. These reports support triage workflows, helping teams prioritize remediation efforts and track compliance progress across test cycles.
SKILL.md
rendered from the published skill — quoted content, verbatim
Accessibility Testing with Selenium WebDriver & Axe Core
This skill enables automated accessibility analysis within the Selenium WebDriver framework using the axe-core engine to detect WCAG violations and best practice issues directly in the browser.
> Activation: This skill is triggered when you need to validate WCAG compliance, scan for accessibility violations, test keyboard navigation, audit ARIA semantics, or generate a11y reports.
First Questions to Ask
- What app URL(s) or user flows are in scope (and what is explicitly out of scope)?
- Is there an existing Selenium setup and how is CI run?
-
Which standard is the target (WCAG 2.1 AA by default), and are there org-specific policies?
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 8 files
skills/accessibility-selenium-testing/LICENSE.txt
skills/accessibility-selenium-testing/SKILL.md
skills/accessibility-selenium-testing/references/axe-api-reference.md
skills/accessibility-selenium-testing/references/axe_patterns.md
skills/accessibility-selenium-testing/references/code-patterns.md
skills/accessibility-selenium-testing/references/wcag21aa-checklist.md
skills/accessibility-selenium-testing/scripts/AccessibilityHelper.java
skills/accessibility-selenium-testing/scripts/pom-template.xml