test-accessibility

Audit web apps for WCAG 2.1 AA using axe-core scans and manual checks.

Updated Mar 26, 2026
One-click install
npx skills add https://github.com/ConductionNL/decidesk --skill test-accessibility
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-accessibility
Source: https://github.com/ConductionNL/decidesk/tree/main/.claude/skills/test-accessibility
Command: npx skills add https://github.com/ConductionNL/decidesk --skill test-accessibility

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Manual accessibility audits are time-consuming and error-prone, especially across complex web apps. This skill combines automated scanning with focused manual checks to help teams meet WCAG 2.1 AA requirements efficiently.

Core Features & Use Cases

  • Automated axe-core scans to identify violations across dashboards, forms, and navigation components.
  • Keyboard navigation validation and focus management checks for interactive UI.
  • Manual WCAG checks and evidence reporting to document compliance for audits and regulatory demands.
  • Use Case: When delivering a new enterprise app, run the accessibility audit to generate a comprehensive report, prioritize issues, and track remediation.

Quick Start

Provide the target app to audit and run the accessibility workflow to generate a ready-to-share report.

Frequently Asked Questions about test-accessibility

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

FAQPage Schema
How do I audit my web app for WCAG 2.1 AA compliance?

To audit a web app for WCAG 2.1 AA compliance, provide the target application to run automated axe-core scans, perform keyboard navigation tests, and generate a structured accessibility report. This combines automated checks with manual verification to identify violations across dashboards, forms, and navigation components.

What is the best way to automate accessibility checks for enterprise apps?

Automating accessibility checks is best done using axe-core to scan interactive UI elements like dashboards and forms. This approach identifies common WCAG 2.1 AA violations quickly, allowing teams to prioritize issues and track remediation efficiently without relying solely on time-consuming manual audits.

How do I validate keyboard navigation and focus management in my UI?

Keyboard navigation and focus management are validated through focused manual checks that test interactive UI components. This ensures users can navigate web apps without a mouse, verifying that focus states are managed correctly and meet WCAG 2.1 AA accessibility requirements.

Does this accessibility testing workflow require any specific dependencies?

No specific dependencies are required to run this accessibility testing workflow. The skill operates independently using built-in axe-core automation and custom checks to scan web apps, meaning no external libraries or modules need to be installed prior to generating an accessibility report.

Why do I need manual WCAG checks if I already use automated scanning?

Manual WCAG checks are needed because automated scanning alone cannot catch all accessibility issues, especially complex keyboard navigation and focus management scenarios. Combining axe-core automation with manual verification ensures comprehensive WCAG 2.1 AA compliance and produces evidence for audits.