accessibility

Name: accessibility
Availability: InStock
Author: AGMO

Detect WCAG accessibility issues in React/HTML/CSS via static review.

4|1|Updated Mar 19, 2026

Search Tags:#accessibility #a11y #frontend #wcag #aria #static-review

Ready to run

npx skills add https://github.com/AGMO-Inc/agmo-everywhere --skill accessibility-agmo-inc

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: accessibility
Source: https://github.com/AGMO-Inc/agmo-everywhere/tree/main/skills/accessibility
Command: npx skills add https://github.com/AGMO-Inc/agmo-everywhere --skill accessibility-agmo-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This WCAG-based static review analyzes frontend/UI changes to identify accessibility issues without modifying code, enabling teams to ship inclusive interfaces faster.

Core Features & Use Cases

Read-only analysis of frontend/UI changes for WCAG conformance.
Severity classification of findings as CRITICAL or MINOR to guide remediation.
Delegated workflow via agmo:explore agent to surface actionable accessibility fixes and evidence.
Output format provides structured findings that can be integrated into design review or CI pipelines.

Quick Start

Inspect the changed frontend files for WCAG issues and generate a structured report.

Frequently Asked Questions about accessibility

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

FAQPage Schema

How do I check my frontend code for WCAG accessibility issues?▼

A static accessibility review analyzes frontend UI changes to identify WCAG issues without modifying code. It checks React, HTML, and CSS for semantic HTML, ARIA, color contrast, and keyboard accessibility problems, returning structured findings.

What is static accessibility review for frontend code?▼

Static accessibility review is a read-only analysis that scans frontend UI changes to identify WCAG conformance issues. It evaluates semantic HTML, ARIA, color contrast, and keyboard accessibility, classifying findings as CRITICAL or MINOR to guide remediation.

Does this accessibility review work with my React and HTML files?▼

Yes, this static accessibility review supports React, HTML, and CSS files. It performs a non-intrusive, read-only analysis on frontend code changes to detect WCAG issues and ARIA misconfigurations across these web technologies.

How are accessibility findings classified during a static UI review?▼

Accessibility findings are classified into CRITICAL and MINOR severity levels. This structured output helps prioritize remediation by distinguishing severe WCAG violations, like keyboard accessibility blocks, from less impactful semantic or contrast issues.

Can I integrate WCAG accessibility checks into a CI pipeline?▼

Yes, you can integrate WCAG accessibility checks into a CI pipeline. The static review generates structured findings based on a deterministic checklist, providing consistent output suitable for automated frontend design review and continuous integration workflows.

What limitations does a static WCAG review have for UI components?▼

A static WCAG review is limited to read-only code analysis and does not execute runtime interactions or visual rendering. It focuses on frontend code changes flagged with accessibility TODOs, meaning it cannot catch dynamic DOM issues or runtime contrast failures.