agentleFS
Sign inStart free
AgnosticUIAgnosticUI/agnosticui/.claude/skills/check-accessibility/SKILL.md

check-accessibility

Skill833 starsChanged 9 months agoApache-2.0View on GitHub

Review component for accessibility issues

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. IndrajeetPatil/effective-claude-code-usage★ 1same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 7 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check accessibility for: $ARGUMENTS

    line 15
  2. Very specific:

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

    line 18
  3. Distinctive:

    Use WebSearch for "WCAG 2.2 [component-type] accessibility"

    line 23
  4. Distinctive:

    Use WebSearch for "ARIA [specific-pattern] best practices"

    line 24
  5. Very specific:

    Check PROJECT_CONTEXT for AgnosticUI's accessibility standards location

    line 30
  6. Distinctive:

    Check if accessibility differs across Lit, React, Vue implementations

    line 43
  7. Distinctive:

    Verify ARIA is applied correctly in each framework's rendering

    line 44
  8. Distinctive:

    Test that events work with keyboard in all frameworks

    line 45
  9. Very specific:

    Ensure fixes align with AgnosticUI's CSS-first approach

    line 56
  10. Distinctive:

    WAIT FOR USER APPROVAL: before implementing

    line 57

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free