accessibility-testing

Automates WCAG 2.2 accessibility checks for web and mobile interfaces via axe-core and CI/CD integration.

Updated Jan 4, 2026
One-click install
npx skills add https://github.com/natea/ai-news-influencer --skill accessibility-testing-natea
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accessibility-testing
Source: https://github.com/natea/ai-news-influencer/tree/main/.claude/skills/accessibility-testing
Command: npx skills add https://github.com/natea/ai-news-influencer --skill accessibility-testing-natea

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Accessibility issues block users with disabilities and can expose organizations to compliance risk. This skill provides automated accessibility testing and validation to help teams meet WCAG 2.2 and inclusive design standards.

Core Features & Use Cases

  • Automated accessibility checks with axe-core to identify violations across web apps.
  • Keyboard navigation and focus management testing to ensure operability without a mouse.
  • Screen-reader validation and color-contrast analysis to verify perceivability for assistive tech users.
  • CI/CD integration to gate builds and releases based on accessibility criteria.
  • Use cases include legal compliance audits, feature development readiness, and pre-release validation across web and mobile interfaces.

Quick Start

Run Accessibility Validation to begin automated WCAG 2.2 checks across your application.

Frequently Asked Questions about accessibility-testing

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

FAQPage Schema
How do I automate WCAG 2.2 accessibility testing in my CI/CD pipeline?

Automate WCAG 2.2 accessibility testing by integrating automated checks into your CI/CD pipeline to gate builds and releases based on accessibility criteria. This skill validates web and mobile interfaces using axe-core, keyboard navigation, and screen-reader checks.

What is the best way to check keyboard navigation and focus management for web apps?

The best way to check keyboard navigation is through automated focus management testing that ensures operability without a mouse. This skill validates keyboard navigation flows alongside color-contrast analysis and screen-reader validation for assistive tech users.

Can I use axe-core to identify WCAG 2.2 violations across mobile interfaces?

Yes, you can use axe-core to identify accessibility violations across both web and mobile interfaces. The skill applies automated axe-core checks to validate perceivability and operability, supporting legal compliance audits and pre-release validation.

Why do I need automated screen-reader validation for pre-release software validation?

Automated screen-reader validation is needed for pre-release validation to verify perceivability for assistive tech users and reduce compliance risk. It helps teams meet WCAG 2.2 inclusive design standards before feature development readiness and legal compliance audits.

Does this approach support color-contrast analysis for legal compliance audits?

Yes, this approach supports color-contrast analysis to verify perceivability during legal compliance audits. It applies automated WCAG 2.2 checks across software projects to identify accessibility issues that block users with disabilities.

When should I run automated accessibility checks during feature development?

Run automated accessibility checks during feature development readiness and pre-release validation to catch violations early. Integrating these checks into your CI/CD pipeline gates builds based on WCAG 2.2 accessibility criteria before legal compliance audits.