ui-accessibility-review

Name: ui-accessibility-review
Availability: InStock
Author: marcus-friction

Identify and fix accessibility and UI quality gaps in Nuxt/Tailwind projects.

3|Updated Feb 9, 2026

Search Tags:#accessibility #a11y #frontend #wcag #tailwind #nuxt

Ready to run

npx skills add https://github.com/marcus-friction/agents --skill ui-accessibility-review

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: ui-accessibility-review
Source: https://github.com/marcus-friction/agents/tree/main/.agent/skills/ui-accessibility-review
Command: npx skills add https://github.com/marcus-friction/agents --skill ui-accessibility-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps development teams ensure frontend UI code is accessible, responsive, and aligned with design-system guidelines, reducing accessibility risks and UI regressions in Nuxt/Tailwind projects.

Core Features & Use Cases

Evaluates WCAG AA compliance, semantic HTML usage, keyboard navigation, and ARIA labeling.
Verifies responsive behavior across breakpoints and enforces token-based design consistency.
Use Case: during a Nuxt/Tailwind UI pass, auditors run this to identify accessibility gaps before shipping to production.

Quick Start

Open a project directory and run a guided accessibility review pass to generate a prioritized report.

Frequently Asked Questions about ui-accessibility-review

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

FAQPage Schema

How do I check WCAG compliance and fix accessibility issues in a Nuxt project?▼

To check WCAG compliance in a Nuxt project, run a guided accessibility review pass that evaluates semantic HTML, keyboard navigation, and ARIA labeling. This generates a prioritized report identifying specific UI accessibility gaps and design-system inconsistencies to fix before production.

What is the best way to audit Tailwind components for keyboard navigation and ARIA usage?▼

Auditing Tailwind components for keyboard navigation and ARIA usage involves evaluating your frontend UI code against WCAG AA standards. A dedicated UI review pass checks for proper semantic HTML structure, accessible labeling, and responsive behavior across breakpoints to ensure full accessibility.

Can I use this accessibility review for design-system audits in Nuxt and Tailwind?▼

Yes, you can use this accessibility review for design-system audits in Nuxt and Tailwind. It verifies token-based design consistency, enforces responsive behavior across breakpoints, and checks WCAG contrast, ensuring your UI components align with established design-system guidelines.

Does this UI review check responsive behavior and WCAG contrast for Tailwind apps?▼

This UI review does check responsive behavior and WCAG contrast for Tailwind apps. It specifies targeted checks for color contrast compliance, responsive layouts across breakpoints, and token-based design consistency, reducing accessibility risks and visual regressions in your Nuxt project.

When should I run an accessibility review pass on my frontend code?▼

You should run an accessibility review pass on your frontend code during UI review passes, frontend feature developments, and design-system audits. Running it before shipping to production helps identify and fix accessibility gaps, ensuring your Nuxt/Tailwind application meets WCAG AA standards.