SkillsAdd

smithery.ai

check-accessibility

Review component for accessibility issues

First seen Mar 20, 2026

Installation

$ npx skills add https://smithery.ai
View on skills.sh ↗ Website ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

flutter-improving-accessibility Similar name
flutter/agent-plugins

Configures a Flutter app to support assistive technologies like Screen Readers. Use when ensuri…

8.5K installs
accessibility-review Similar name
anthropics/knowledge-work-plugins

Run a WCAG 2.1 AA accessibility audit on a design or page. Trigger with "audit accessibility", …

3.4K installs
accessibility Similar name
microsoft/vscode

Primary accessibility skill for VS Code. REQUIRED for new feature and contribution work, and al…

2.8K installs
flutter-accessibility-audit Similar name
flutter/agent-plugins

Triggers an accessibility scan through the widget_inspector and automatically adds Semantics wi…

1.5K installs
webflow-mcp:accessibility-audit Similar name
webflow/webflow-skills

Run comprehensive accessibility audit (WCAG 2.1) on Webflow pages - checks buttons, forms, link…

706 installs
accessibility Similar name
addyosmani/web-quality-skills

Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve a…

51.2K installs

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai
smithery-ai-cli 7.8K frontend-design 6.2K skill-creator 2.5K ck:ui-ux-pro-max 1.3K pdf 1.2K xlsx 966 pptx 894 docx 884 webapp-testing 1 web-design-reviewer 657

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Allowed toolsRead, Grep, Glob, WebSearch, WebFetch
Declared agents claude-code

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,540 B
  • docs SUMMARY.md 68 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

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

  1. 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

  1. 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

  1. 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

  1. 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

  1. 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