Accessibility Reviewer logo

Accessibility Reviewer

Community
dev-ik
accessibility-reviewer

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.

Overview

Publisherdev-ik
Repositoryai-design-rules
Skill nameaccessibility-reviewer
Stars
3
Forks
0
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by dev-ik on GitHub. Read the source before you install it.

Installation

Install the Accessibility Reviewer AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/dev-ik/ai-design-rules/tree/main/skills/accessibility-reviewer
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/dev-ik/ai-design-rules.git /tmp/ai-design-rules
mkdir -p .claude/skills
cp -r /tmp/ai-design-rules/skills/accessibility-reviewer .claude/skills/accessibility-reviewer
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Accessibility Reviewer in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Accessibility Reviewer on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Accessibility Reviewer is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

md
## 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.

Frequently asked questions

What does the Accessibility Reviewer AI skill do?

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.

Why use Accessibility Reviewer on TypingMind?

Because you install it once and use it with any model. Accessibility Reviewer is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Accessibility Reviewer in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/dev-ik/ai-design-rules/tree/main/skills/accessibility-reviewer. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Accessibility Reviewer?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Accessibility Reviewer?

As many as you like. As long as a model supports skills, you can use Accessibility Reviewer with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Accessibility Reviewer AI skill free?

Yes. It is published on GitHub by dev-ik under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇