accessibility-test-generator

Name: accessibility-test-generator
Availability: InStock
Author: mouayadakel

Generate accessibility tests for axe-core violations, keyboard navigation, focus traps, and ARIA attributes.

Updated Feb 3, 2026

Search Tags:#testing #accessibility #a11y #keyboard navigation #ARIA #axe-core

Ready to run

npx skills add https://github.com/mouayadakel/flixCamFinal --skill accessibility-test-generator

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: accessibility-test-generator
Source: https://github.com/mouayadakel/flixCamFinal/tree/main/.cursor/skills/accessibility-test-generator
Command: npx skills add https://github.com/mouayadakel/flixCamFinal --skill accessibility-test-generator

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of generating comprehensive accessibility tests for web interfaces, ensuring compliance and usability for all users.

Core Features & Use Cases

Automated Testing: Generates tests for axe-core, keyboard navigation, focus traps, and ARIA compliance.
Integration: Can be used with E2E or component testing frameworks like Playwright or Jest.
Use Case: When developing a new UI component, use this Skill to automatically generate a suite of accessibility tests to catch issues early in the development cycle.

Quick Start

Use the accessibility-test-generator skill to generate axe-core and keyboard navigation tests for the current page.

Frequently Asked Questions about accessibility-test-generator

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

FAQPage Schema

How do I generate automated accessibility tests for axe-core violations?▼

Automated accessibility tests for axe-core violations are generated by creating test suites that check UI components for compliance, keyboard navigation order, focus trap implementation, and ARIA attribute correctness. These tests integrate with frameworks like Playwright or Jest-axe for execution.

What is automated ARIA attribute correctness testing?▼

Automated ARIA attribute correctness testing validates that web interface components have proper ARIA roles, states, and properties applied, ensuring screen reader compatibility and compliance when integrated with testing frameworks like Playwright or Jest.

Does this accessibility testing approach work with Playwright and Jest?▼

Yes, generated accessibility tests covering axe-core, keyboard navigation, and focus traps are designed for integration with E2E or component testing frameworks like Playwright or Jest-axe for execution during UI development and pre-deployment checks.

How do I test keyboard navigation order and focus traps in web applications?▼

Keyboard navigation order and focus trap implementation are tested by generating automated test scripts that simulate keyboard interactions, verifying that focus moves logically and remains contained within UI components during pre-deployment checks.

When do I need automated accessibility testing for UI component development?▼

Automated accessibility testing is needed during UI component development to catch axe-core violations, keyboard navigation issues, and ARIA compliance errors early in the development cycle before web application deployment.