skills.rest
foutoucour
foutoucourCOMMUNITY
Explore all skills by this author →
𝕏@jordiriera_cgGitHub

accessibility-audit

Audit frontend accessibility issues against WCAG 2.1 AA standards.

Updated Mar 24, 2026
Search Tags:#accessibility#contrast#aria#keyboard-navigation#frontend-audit#wcag-2.1
One-click install
npx skills add https://github.com/foutoucour/guitar-match --skill accessibility-audit-foutoucour
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility-audit
Source: https://github.com/foutoucour/guitar-match/tree/main/.claude/skills/accessibility-audit
Command: npx skills add https://github.com/foutoucour/guitar-match --skill accessibility-audit-foutoucour

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill assists teams in identifying and addressing frontend accessibility issues to meet WCAG 2.1 AA standards, ensuring usable interfaces for all users.

Core Features & Use Cases

  • Semantic HTML checks to ensure proper landmark elements and heading structure.
  • ARIA and keyboard navigation validation to fix roles, labels, and focus management.
  • Color contrast evaluation and screen reader compatibility recommendations for common UI patterns.
  • Use Case: Run an audit on a React app's login form to surface missing labels, incorrect ARIA roles, and focus trap issues.

Quick Start

Scan your frontend project to generate an accessibility report that highlights WCAG 2.1 AA issues.

Frequently Asked Questions about accessibility-audit

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

FAQPage Schema
How do I audit frontend code for WCAG 2.1 AA accessibility issues?▼

Run an accessibility audit on your frontend project to identify WCAG 2.1 AA issues across semantic HTML, ARIA roles, keyboard navigation, color contrast, and screen reader compatibility.

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

An accessibility audit checks for proper semantic HTML structure, ARIA roles, keyboard navigation, focus management, color contrast, and screen reader compatibility to ensure inclusive web interfaces.

How do I fix keyboard navigation and focus trap issues in a React login form?▼

To fix keyboard navigation and focus trap issues, validate ARIA roles, correct focus management, and add missing form labels to ensure proper assistive technology interaction and screen reader compatibility.

Can I use this accessibility audit for screen reader compatibility checks?▼

Yes, you can use this audit to evaluate screen reader compatibility by identifying incorrect ARIA roles, missing labels, and focus management issues that affect assistive technology interaction.

Does this WCAG audit check color contrast and semantic HTML structure?▼

Yes, this audit evaluates color contrast insufficiencies and validates semantic HTML structure to ensure proper landmark elements and heading structure for accessible web interfaces.

Related Skills

Explore More Software Engineering Skills→
yutanpo1227yutanpo1227

web-design-guidelines

Audit UI code against Web Interface Guidelines for accessibility and design compliance.

Community
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
kennedym-dskennedym-ds
14

accessibility-wcag

Evaluate and implement WCAG 2.1 AA accessibility patterns for frontend web development.

Community
Advanced
ryan-nguyen-01ryan-nguyen-01
4

skill-ui-accessibility

Analyze web UI structure, semantics, and ARIA usage for accessibility gaps.

Community
Advanced