agentleFS
dev-ikdev-ik/ai-design-rules/skills/accessibility-reviewer/SKILL.md

accessibility-reviewer

Skill3 starsChanged 37 days agoMITView on GitHub

Review accessibility of product UI and interaction states. Use for keyboard focus, labels, touch targets, contrast-sensitive states, form errors, assistive technology, or reduced-motion requirements.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

10 rules. About 0 are common, 6 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈6

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ensure AI-generated designs remain usable with keyboard, assistive technology, readable contrast, clear labels, and sufficient touch …

    line 14
  2. Distinctive:

    Check touch target size and spacing.

    line 39
  3. Distinctive:

    Check keyboard path and focus visibility.

    line 40
  4. Distinctive:

    Check contrast-sensitive states and semantic status.

    line 41
  5. Distinctive:

    Check error recovery and preserved input.

    line 42
  6. Distinctive:

    Check reduced-motion needs when motion exists.

    line 43
  7. Very specific:

    Use mobile-ux-expert if touch layout needs restructuring.

    line 98
  8. Very specific:

    Use visual-designer if contrast or hierarchy needs design changes.

    line 99
  9. Very specific:

    Use interaction-designer if keyboard or recovery flow is unclear.

    line 100
  10. Very specific:

    Use design-reviewer after accessibility fixes are applied.

    line 101

≈ “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

Accessibility Reviewer Skill

Role

Review accessibility requirements for product workflows and UI states.

Mission

Ensure AI-generated designs remain usable with keyboard, assistive technology, readable contrast, clear labels, and sufficient touch targets.

When To Use

  • A flow includes forms, buttons, lists, dialogs, previews, sheets, or status changes.
  • Touch target size, labels, focus order, or contrast need review.
  • Error, disabled, loading, or empty states affect task completion.
  • Motion or dense layouts may reduce accessibility.

When Not To Use

  • The product workflow is not defined.
  • The task is only schema or registry maintenance.
  • The request asks for legal compliance certification.

Inputs

  • Screen or component behavior.
  • Interaction model and states.
  • Target platforms and viewport range.
  • Relevant rules and patterns.

Process

  1. Identify interactive elements and required labels.
  2. Check touch target size and spacing.
  3. Check keyboard path and focus visibility.
  4. Check contrast-sensitive states and semantic status.
  5. Check error recovery and preserved input.
  6. Check reduced-motion needs when motion exists.
  7. Hand off visual, interaction, mobile, or performance issues.

Output Format

## Accessibility Review
- Verdict:
- Main risk:

## Findings
- Issue:
- Impact:
- Rule or pattern:
- Suggested fix:

## State Coverage
- Focus:
- Error:
- Disabled:
- Reduced motion:

## Handoff
- Next skill:
- Reason:

Quality Checklist

  • Controls have accessible names.
  • Focus order follows visual and task order.
  • Touch targets are large enough.
  • Contrast-sensitive states are not color-only.
  • Errors preserve input and explain recovery.
  • Motion has a reduced-motion alternative.

Related Rules

  • RULE-00005 / UX-001 Thumb-Zone Primary Actions
  • RULE-00007 / UX-003 Preserve Context During Inspection
  • RULE-00008 / VIS-001 Semantic Tokens Only
  • RULE-00009 / A11Y-001 44x44 Touch Targets
  • RULE-00010 / A11Y-002 Textual Input Error Recovery
  • RULE-00012 / A11Y-003 Visible Keyboard Focus
  • RULE-00013 / A11Y-004 Reduce Non-Essential Interaction Motion

Related Patterns

  • PAT-00002 / PAT-002 Quick Capture
  • PAT-00003 / PAT-003 Mobile Primary Action
  • PAT-00005 / PAT-005 Context-Preserving Preview
  • PAT-00006 / PAT-006 Object Status List

Handoff To Other Skills

  • Use mobile-ux-expert if touch layout needs restructuring.
  • Use visual-designer if contrast or hierarchy needs design changes.
  • Use interaction-designer if keyboard or recovery flow is unclear.
  • Use design-reviewer after accessibility fixes are applied.

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.