accessibility-testing

Run automated and manual accessibility tests with axe-core and Lighthouse.

39|2|Updated Jan 31, 2026

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

Ready to run

npx skills add https://github.com/hffmnnj/opencode-goopspec --skill accessibility-testing-hffmnnj

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: accessibility-testing
Source: https://github.com/hffmnnj/opencode-goopspec/tree/main/skills/accessibility-testing
Command: npx skills add https://github.com/hffmnnj/opencode-goopspec --skill accessibility-testing-hffmnnj

SYSTEM DOCUMENTATION & REQUIREMENTS

## What problem does it solve? Systematically verify accessibility compliance across web interfaces, reducing undetected WCAG violations and ensuring inclusive user experiences.

## Core Features & Use Cases

Automated Accessibility Testing: run axe-core or similar tools on web pages to detect accessibility issues.
CI/CD Integration: integrate accessibility checks into your pipeline to catch regressions automatically.
Manual Testing Guidance: verify keyboard navigation, screen reader compatibility, focus order, and dynamic content updates.
Use Case: QA engineer uses automated tests on every deploy and performs targeted manual checks for critical components.

Quick Start

Use the skill to start automated accessibility checks on a sample web page using axe-core and Lighthouse, then validate results in your CI pipeline.

Frequently Asked Questions about accessibility-testing

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

FAQPage Schema

How do I automate accessibility testing in my CI/CD pipeline?▼

Automate accessibility testing by integrating axe-core or Lighthouse checks into your deployment pipeline to catch WCAG violations before release. Run these tools on every build to detect regressions automatically and ensure compliance across web pages and UI components.

What accessibility issues can automated tools like axe-core detect?▼

Automated tools detect WCAG violations including missing alt text, color contrast failures, improper heading hierarchy, form labeling errors, and keyboard navigation barriers. They scan web pages systematically but require manual testing for dynamic content and screen reader compatibility.

How do I test keyboard navigation and screen reader compatibility?▼

Manual testing for keyboard navigation involves tabbing through focus order and verifying all interactive elements are reachable. Screen reader validation requires testing with assistive technology to confirm dynamic content updates, ARIA labels, and semantic structure work correctly across components.

Can I use accessibility testing tools with Lighthouse in the same workflow?▼

Yes, combine axe-core and Lighthouse checks in the same testing workflow. Lighthouse provides broader performance and accessibility audits while axe-core offers deeper WCAG-specific violation detection, allowing comprehensive coverage across CI/CD pipelines and manual QA sessions.

What's the difference between automated and manual accessibility testing?▼

Automated testing with axe-core and Lighthouse identifies common WCAG violations quickly at scale. Manual testing validates keyboard navigation, focus order, screen reader behavior, and dynamic content—catching issues automation misses and ensuring truly inclusive user experiences.

Do I need special setup to run accessibility checks on every deploy?▼

Set up accessibility checks as pipeline tasks to run automatically on every deployment. Most tools integrate with standard CI/CD systems and require minimal configuration beyond pointing them to your web application URLs or component test environments.