a11y-check

Analyze web interfaces for WCAG 2.1 AA accessibility compliance.

Updated Nov 19, 2025
One-click install
npx skills add https://github.com/tubone24/tubone-ui-skills --skill a11y-check-tubone24
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: a11y-check
Source: https://github.com/tubone24/tubone-ui-skills/tree/main/.claude/skills/a11y-check
Command: npx skills add https://github.com/tubone24/tubone-ui-skills --skill a11y-check-tubone24

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps identify and fix accessibility issues in web interfaces, ensuring compliance with WCAG standards and improving usability for all users.

Core Features & Use Cases

  • Keyboard Navigation Checks: Verifies that all interactive elements are focusable and operable via keyboard.
  • Semantic HTML Validation: Assesses the correct usage of HTML elements for structure and meaning.
  • ARIA Usage Guidance: Provides recommendations on appropriate ARIA attribute implementation.
  • Color Contrast Analysis: Checks text and UI element contrast ratios against WCAG AA and AAA standards, including dark mode considerations.
  • Dynamic Content Handling: Reviews accessibility for elements like modals, loading states, and error messages.
  • Use Case: A developer can use this skill to audit a new feature for keyboard traps, incorrect heading structures, and insufficient color contrast before release.

Quick Start

Run an accessibility check on the provided web page URL.

Frequently Asked Questions about a11y-check

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

FAQPage Schema
How do I check my web interface for WCAG 2.1 AA compliance?

To check WCAG 2.1 AA compliance, audit your web interface for keyboard operability, semantic HTML structure, ARIA implementation, and color contrast ratios. This process identifies accessibility barriers and provides actionable code examples for remediation.

What is the best way to test keyboard navigation and focus traps in web apps?

The best way to test keyboard navigation is verifying that all interactive elements are focusable and operable without creating keyboard traps. Analyzing keyboard operability ensures users navigating without a mouse can access all dynamic content effectively.

How do I validate color contrast ratios for dark mode against WCAG standards?

To validate color contrast ratios for dark mode, analyze text and UI element contrast against WCAG AA and AAA standards. Checking dark mode considerations ensures sufficient luminance differences for visually impaired users navigating your interface.

Can I get ARIA implementation guidance for dynamic content like modals and loading states?

Yes, you can get ARIA implementation guidance by reviewing dynamic content accessibility for modals, loading states, and error messages. This analysis provides recommendations on appropriate ARIA attribute implementation to ensure dynamic updates are announced correctly.

Does this accessibility audit check semantic HTML structure and heading hierarchy?

Yes, this accessibility audit checks semantic HTML structure by assessing the correct usage of HTML elements for structure and meaning. Validating heading structures and semantic elements ensures screen readers can accurately interpret and navigate your web content.