Check Accessibility
Designcheck-accessibilityCheck Accessibility is an Agent Skill for design published in the AgnosticUI/agnosticui repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
Review component for accessibility issues
QUICK START
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/AgnosticUI/agnosticui/blob/HEAD/.claude/skills/check-accessibility/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/check-accessibility, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
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.mdfor 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
- Core component:
-
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