AugmentClaude
FrontendAccessibility

Accessibility Checker

By AgnosticUI· AgnosticUI/agnosticui· 0

Review components for accessibility issues and WCAG compliance.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.
    Install
    Sign up to copy
    Sign up free to reveal

    This copies the whole skill folder into ~/.claude/skills/check-accessibility-agnosticui/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
    Sign up free to reveal
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

Review component for accessibility issues

What this skill does

Usage: /check-accessibility COMPONENT_NAME

Examples:

  • /check-accessibility button
  • /check-accessibility alert
  • /check-accessibility v2/lib/src/components/Button.ts

Check accessibility for: $ARGUMENTS

Setup:

  1. Read .claude/PROJECT_CONTEXT.md for AgnosticUI structure and accessibility principles

Process:

  1. Search for latest standards:

    • Use WebSearch for "WCAG 2.2 [component-type] accessibility"
    • Use WebSearch for "ARIA [specific-pattern] best practices"
    • Fetch W3C WAI-ARIA documentation if needed for specific patterns

  2. Locate component files:

    • Core component: v2/lib/src/components/$ARGUMENTS*
    • Framework implementations if relevant: v2/playgrounds/*/src/stories/*$ARGUMENTS*
    • Check PROJECT_CONTEXT for AgnosticUI's accessibility standards location

  3. Analyze against current standards:

    • Semantic HTML: Proper element usage for meaning and structure
    • ARIA attributes: Correct, necessary, and following latest specs
    • Keyboard navigation: Tab order, focus management, keyboard shortcuts
    • Focus indicators: Visible focus styles meeting contrast requirements
    • Screen reader support: Meaningful labels, descriptions, live regions
    • Color contrast: WCAG 2.2 AA requirements (4.5:1 text, 3:1 UI)
    • Touch targets: Minimum 44x44px for interactive elements
    • Motion/animation: Respects prefers-reduced-motion

  4. Framework-specific considerations:

    • Check if accessibility differs across Lit, React, Vue implementations
    • Verify ARIA is applied correctly in each framework's rendering
    • Test that events work with keyboard in all frameworks

  5. Report findings:

    • List issues with severity (Critical/High/Medium/Low)
    • Reference specific WCAG 2.2 success criteria
    • Provide remediation steps with code examples
    • Link to current W3C/MDN documentation
    • Note AgnosticUI-specific patterns to follow

  6. If fixes requested:

    • Propose changes that work across all frameworks
    • Ensure fixes align with AgnosticUI's CSS-first approach
    • WAIT FOR USER APPROVAL before implementing

AgnosticUI Accessibility Requirements:

  • WCAG 2.1 AA compliance minimum
  • Framework-agnostic solutions preferred
  • CSS custom properties for focus indicators
  • Consistent behavior across Lit, React, Vue

Related skills

G

Generative Code Art

anthropics

Create algorithmic art with p5.js using randomness and interactive parameters.

OfficialComplete terms in LICENSE.txt
U

UI/UX Pro Max

anthropics

Build production-grade web components and interfaces with distinctive, polished design.

OfficialComplete terms in LICENSE.txt
A

Artifact Theme Toolkit

anthropics

Apply professional color and font themes to slides, docs, and web pages.

OfficialComplete terms in LICENSE.txt
M

Multi-Component Web Artifacts

anthropics

Build complex React artifacts with Tailwind CSS and shadcn/ui components.

OfficialComplete terms in LICENSE.txt