skills.rest
haabe
haabeCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

a11y-check

Audits web interfaces for WCAG 2.1 AA accessibility compliance.

Updated Apr 7, 2026
Search Tags:#testing#accessibility#a11y#wcag#keyboard#screen-reader#aria
One-click install
npx skills add https://github.com/haabe/tic-tac-toe --skill a11y-check-haabe
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: a11y-check
Source: https://github.com/haabe/tic-tac-toe/tree/main/.claude/skills/a11y-check
Command: npx skills add https://github.com/haabe/tic-tac-toe --skill a11y-check-haabe

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Accessibility audit against WCAG 2.1 AA. Checks semantic HTML, ARIA, keyboard navigation, color contrast, screen reader compatibility.

Core Features & Use Cases

  • Identify WCAG 2.1 AA failures such as missing alt text, color contrast issues, improper ARIA roles, or keyboard focus problems.
  • Provide actionable guidance to fix issues during development and QA.
  • Integrate into CI to prevent accessibility regressions.

Quick Start

Run the a11y-check audit on your web page to detect WCAG 2.1 AA violations.

Frequently Asked Questions about a11y-check

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 accessibility compliance?▼

To audit web interfaces for WCAG 2.1 AA accessibility, run checks on your HTML pages to identify compliance gaps in semantic markup, ARIA roles, and keyboard navigation. It scans components to detect missing labels and focus management issues.

What does a WCAG 2.1 AA accessibility audit check for?▼

A WCAG 2.1 AA accessibility audit checks for semantic HTML, ARIA usage, keyboard navigation, color contrast, and screen reader compatibility. It enforces accessible markup, proper labeling, and focus management to identify conformance failures.

Can I integrate accessibility testing into my CI pipeline to prevent regressions?▼

Yes, you can integrate accessibility testing into your CI pipeline to prevent regressions. Running audits during development and QA provides actionable guidance to fix WCAG 2.1 AA violations before deployment.

How do I fix keyboard navigation and screen reader compatibility issues in HTML?▼

To fix keyboard navigation and screen reader compatibility issues, audit your HTML for proper ARIA roles, semantic markup, and focus management. This identifies WCAG 2.1 AA failures and provides actionable guidance to correct them.

Related Skills

Explore More Software Engineering Skills→
Hack23Hack23
9

html-accessibility

Audit static HTML/CSS sites and implement WCAG 2.1 AA accessibility improvements.

Official
Intermediate
PrasadTelasulaPrasadTelasula

accessibility-compliance

Implement WCAG 2.1 AA accessibility across QA Team Portal interfaces with ARIA roles, keyboard navigation, and color contrast fixes.

Community
Advanced
timsvoicetimsvoice

specimin-ui-accessibility

Audit and fix generated UI code for WCAG 2.1 AA compliance.

Community
Advanced
89jobrien89jobrien
4

web-accessibility

Audit web content for WCAG 2.1/2.2 conformance and accessibility issues.

Community
Advanced