Check Accessibility Skill for Claude

by AgnosticUI

Review component for accessibility issues

635 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

822

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/AgnosticUI/agnosticui --skill check-accessibility

The instruction itself

as written by the author

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:

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

Process:

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

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

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

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

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

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

Other skills for the same job

different authors, same section of the catalogue

Theme Factory

by anthropics

vendor ×16

Toolkit for styling artifacts with a theme. These artifacts can be slides, docs, reportings, HTML landing pages, etc. There are 10 pre-set themes with colors/fonts that you can apply to any artifact that has been creating, or can generate a new theme on-the-fly.

Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.

Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.

11k tokens scripts

Web Artifacts Builder

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.

Set up Tailwind CSS v4 in Expo with react-native-css and NativeWind v5 for universal styling

Use Expo DOM components to run web code in a webview on native and as-is on web. Migrate web code to native incrementally.

3k tokens

How to use it

Copy the folder

Take agnosticui/check-accessibility from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.