frontend-accessibility-review

Audit web frontends for WCAG 2.2 AA conformance with static and live checks.

1|Updated Apr 29, 2026

Search Tags:#frontend development #accessibility review #web accessibility #semantics #WCAG 2.2 AA

Ready to run

npx skills add https://github.com/sigmadigitalza/engineering-playbook --skill frontend-accessibility-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: frontend-accessibility-review
Source: https://github.com/sigmadigitalza/engineering-playbook/tree/main/plugins/sigma-engineering/skills/frontend-accessibility-review
Command: npx skills add https://github.com/sigmadigitalza/engineering-playbook --skill frontend-accessibility-review

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill unit provides a comprehensive review of web frontends for WCAG 2.2 Level AA accessibility, ensuring semantic HTML, ARIA, keyboard interaction, screen reader experience, color contrast, forms, motion, and internationalization are in place.

Core Features & Use Cases

Static Code Review: Analyze components, pages, and design system primitives without a live site.
Live Site Audit: Conduct automated and manual reviews of deployed URLs, including axe-core, Lighthouse, keyboard sweep, and screen reader smoke test.
Detailed Reporting: Generate a report with confirmed failures, risks, and manual checks, including critical issues that block user tasks.

Quick Start

Use the frontend-accessibility-review skill to review the 'frontend-component.html' file for accessibility issues.

Frequently Asked Questions about frontend-accessibility-review

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

FAQPage Schema

How do I conduct a WCAG 2.2 AA accessibility review on a live website?▼

To conduct a WCAG 2.2 AA accessibility review on a live website, perform automated audits with axe-core and Lighthouse, execute a keyboard sweep, and run screen reader smoke tests to identify conformance failures.

What does static code analysis check for in web accessibility reviews?▼

Static code analysis in web accessibility reviews checks semantic HTML, ARIA attributes, and design system primitives directly within component files to identify WCAG 2.2 AA conformance issues without needing a deployed URL.

Can I use automated tooling to replace manual screen reader testing for WCAG conformance?▼

Automated tooling cannot fully replace manual screen reader testing for WCAG conformance because automated tools primarily detect structural code errors, while manual testing validates actual user experience, keyboard navigation, and motion constraints.

How do I audit semantic HTML and ARIA for frontend accessibility?▼

To audit semantic HTML and ARIA for frontend accessibility, analyze component code to verify correct landmark usage, roles, and states, ensuring all interactive elements meet WCAG 2.2 AA standards for screen reader compatibility.

What is included in a frontend accessibility review report?▼

A frontend accessibility review report includes confirmed WCAG 2.2 AA failures, potential risks requiring manual checks, and critical issues that block user tasks, providing a comprehensive overview of conformance gaps.