accessibility-selenium-testing

Automate WCAG compliance scans by integrating axe-core with Selenium WebDriver.

215|38|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/fugazi/test-automation-skills-agents --skill accessibility-selenium-testing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-selenium-testing
Source: https://github.com/fugazi/test-automation-skills-agents/tree/main/skills/accessibility-selenium-testing
Command: npx skills add https://github.com/fugazi/test-automation-skills-agents --skill accessibility-selenium-testing

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill reduces the manual effort of verifying web accessibility by integrating axe-core with Selenium to identify WCAG issues directly in automated tests.

Core Features & Use Cases

  • Automated accessibility scans across web pages and components with axe-core inside Selenium-driven flows.
  • Keyboard navigation and ARIA semantics checks, color-contrast audits, and pour-principle alignment.
  • Generate structured accessibility reports and filter results by impact for CI integration and remediation planning.

Quick Start

Integrate axe-core with your Selenium tests and run accessibility scans on target pages using the provided utilities.

Frequently Asked Questions about accessibility-selenium-testing

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate web accessibility testing with Selenium?

You can automate web accessibility testing by integrating axe-core with Selenium WebDriver to scan pages for WCAG 2.1/2.2 compliance and generate a11y violation reports. This Skill provides utilities to execute scans directly within your automated test flows.

What is axe-core used for in automated a11y testing?

Axe-core is used in automated a11y testing to evaluate web pages for WCAG violations, including ARIA semantics checks and color-contrast audits. Integrating it with Selenium WebDriver allows you to validate keyboard navigation and pour-principle alignment programmatically.

Can I filter accessibility violations by impact level in CI pipelines?

Yes, you can filter accessibility violations by impact level in CI pipelines. The Skill provides utilities for result logging and filtering by impact, allowing you to generate structured accessibility reports and Allure attachments for remediation planning.

Does this Selenium accessibility testing approach require a specific Java version?

Yes, this Selenium accessibility testing approach requires Java 21 or higher and Selenium WebDriver 4 or above. You need this environment setup to properly integrate axe-core and execute the automated a11y scans.

What is the best way to audit color contrast and keyboard navigation in web applications?

The best way to audit color contrast and keyboard navigation is by running automated axe-core scans through Selenium WebDriver. This approach validates WCAG 2.1/2.2 compliance across targeted components and logs structured results for remediation.