skills.rest
arcasilesgroup
arcasilesgroupOFFICIAL
Explore all skills by this author →
WebsiteGitHub

accessibility

Review frontend code for WCAG 2.1 AA compliance and report actionable findings.

54|3|Updated Feb 4, 2026
Search Tags:#accessibility#a11y#screen reader#keyboard navigation#frontend#compliance#wcag
One-click install
npx skills add https://github.com/arcasilesgroup/ai-engineering --skill accessibility-arcasilesgroup
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/arcasilesgroup/ai-engineering/tree/main/.agents/skills/accessibility
Command: npx skills add https://github.com/arcasilesgroup/ai-engineering --skill accessibility-arcasilesgroup

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill addresses the critical need to make digital products usable by everyone, regardless of ability, by identifying and rectifying accessibility barriers in frontend code.

Core Features & Use Cases

  • WCAG 2.1 AA Compliance Review: Audits code against semantic HTML, ARIA patterns, keyboard navigation, color contrast, and screen reader support.
  • Actionable Findings: Provides severity-tagged remediation suggestions with code examples.
  • Use Case: Before launching a new user interface, run this Skill to ensure it meets accessibility standards, preventing exclusion of users with disabilities and avoiding compliance issues.

Quick Start

Run the accessibility skill to review the current frontend code for WCAG 2.1 AA compliance.

Frequently Asked Questions about accessibility

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

Audit frontend code for WCAG 2.1 AA compliance by analyzing semantic HTML, ARIA patterns, keyboard navigation, color contrast, and screen reader support to identify and report actionable findings with severity and remediation steps.

What is the best way to fix ARIA patterns and keyboard navigation issues in UI components?▼

Fix ARIA patterns and keyboard navigation issues by reviewing UI components and framework-specific patterns against WCAG 2.1 AA standards, which yields severity-tagged remediation suggestions with code examples.

Does this accessibility review cover framework-specific UI components and semantic HTML?▼

Yes, this accessibility review covers framework-specific UI components and semantic HTML, requiring analysis of these patterns to ensure they meet WCAG 2.1 AA compliance standards.

How do I check my web application for screen reader support and color contrast compliance?▼

Check screen reader support and color contrast compliance by running an accessibility review that targets these specific areas alongside semantic HTML and keyboard navigation to ensure WCAG 2.1 AA adherence.

Why does my frontend code fail WCAG 2.1 AA accessibility standards?▼

Frontend code fails WCAG 2.1 AA accessibility standards due to missing semantic HTML, incorrect ARIA patterns, poor keyboard navigation, insufficient color contrast, or inadequate screen reader support, which this review identifies.

When do I need to run an accessibility compliance review on my frontend code?▼

Run an accessibility compliance review before launching a new user interface to ensure it meets WCAG 2.1 AA standards, preventing the exclusion of users with disabilities and avoiding compliance issues.

Related Skills

Explore More Software Engineering Skills→
arcasilesgrouparcasilesgroup
54

ai-accessibility

Review frontend code for WCAG 2.1 AA compliance with severity-tagged remediation.

Official
Advanced
berkcangumusisikberkcangumusisik
11

accessibility-audit

Audit React/HTML components for WCAG 2.1 accessibility issues.

Community
Intermediate
kennedym-dskennedym-ds
14

accessibility-wcag

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

Community
Advanced
houkehouke

accessibility-audit

Automate WCAG accessibility audits for web components using axe-core.

Community
Advanced