skills.rest
robotijn
robotijnCOMMUNITY
Explore all skills by this author →
GitHub

accessibility-checker

Scan web applications for WCAG 2.2 Level AA conformance and generate triaged compliance reports.

3|2|Updated Jan 23, 2026
Search Tags:#accessibility#a11y#compliance#wcag#axe-core#web-app#ada
One-click install
npx skills add https://github.com/robotijn/ctoc --skill accessibility-checker-robotijn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility-checker
Source: https://github.com/robotijn/ctoc/tree/main/skills/specialized/accessibility-checker
Command: npx skills add https://github.com/robotijn/ctoc --skill accessibility-checker-robotijn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Web applications often fail to meet accessibility standards, excluding users with disabilities and exposing organizations to legal penalties under regulations like the European Accessibility Act, ADA Title II, and Section 508. This Skill catches WCAG 2.2 AA compliance failures early in the development cycle, before they reach production or trigger audits.

Core Features & Use Cases

  • Multi-engine automated scanning: Runs axe-core, IBM Equal Access, Pa11y, and Lighthouse against rendered DOM surfaces across mobile and desktop viewports to catch contrast failures, missing labels, focus traps, and other common issues.
  • Manual review checklists: Covers gaps automation misses, including keyboard navigation order, screen reader coherence, alt text quality, and reduced motion support.
  • Compliance reporting: Generates triaged findings aligned with WCAG 2.2 POUR principles, with severity ratings, suggested fixes, and baseline tracking for CI/CD gating.
  • Use Case: A SaaS development team can audit their user onboarding flow to identify and fix missing form labels, low-contrast text, and inaccessible modal dialogs before launch, avoiding costly post-release remediation and regulatory fines.

Quick Start

Use the accessibility-checker skill to audit the WCAG 2.2 AA compliance of your web application's user authentication flow.

Frequently Asked Questions about accessibility-checker

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

FAQPage Schema
How do I check my web app for WCAG 2.2 AA compliance before launch?▼

Check WCAG 2.2 AA compliance by running multi-engine automated scans with axe-core and IBM Equal Access against rendered DOM surfaces, supplemented by manual review checklists for keyboard navigation and screen reader coherence to catch issues before launch.

What is the best way to automate accessibility testing for ADA and Section 508 compliance?▼

Automate accessibility testing for ADA and Section 508 compliance by integrating multi-engine scans across mobile and desktop viewports, generating triaged compliance reports with severity ratings and suggested fixes to support CI/CD gating and regulatory audit readiness.

Can automated accessibility scanners detect keyboard navigation and screen reader issues?▼

Automated accessibility scanners cannot fully detect keyboard navigation order or screen reader coherence, so manual review checklists are necessary to cover gaps automation misses, including alt text quality and reduced motion support.

Does axe-core work for testing European Accessibility Act compliance in web applications?▼

axe-core works for testing European Accessibility Act compliance in web applications by scanning rendered DOM surfaces for contrast failures, missing labels, and focus traps, producing triaged findings aligned with WCAG 2.2 POUR principles.

How do I generate accessibility compliance reports for CI/CD gating?▼

Generate accessibility compliance reports for CI/CD gating by running automated engines like Pa11y and Lighthouse, which produce triaged findings with severity ratings, suggested fixes, and baseline tracking to block deployments with critical violations.

What accessibility issues should I look for when auditing a user onboarding flow?▼

When auditing a user onboarding flow for accessibility issues, look for missing form labels, low-contrast text, and inaccessible modal dialogs across mobile and desktop viewports to avoid costly post-release remediation and regulatory fines.

Related Skills

Explore More Software Engineering Skills→
Luqman-Ud-DinLuqman-Ud-Din

qa-detect-typography-responsive

Detect responsive typography and legibility defects across mobile, tablet, and desktop viewports.

Community
Intermediate
ethanolivertroyethanolivertroy
3

compliance-tracker

Track compliance status across multiple frameworks and identify gaps.

Community
Advanced
CENKSSSCENKSSS

a11y-ally

Audit web accessibility with axe-core, pa11y, and Lighthouse.

Community
Advanced
Luqman-Ud-DinLuqman-Ud-Din

qa-detect-forced-colors

Detect forced-colors accessibility failures in rendered web pages.

Community
Intermediate