Accessibility Review

Organization

getcrew44

accessibility-review

Use to audit a design or page for WCAG 2.1 AA — contrast, keyboard, focus, labels, touch targets, screen reader behavior.

Overview

Publisher	getcrew44
Repository	`crew44`
Skill name	`accessibility-review`
Stars	357
Forks	12
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

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 getcrew44 on GitHub. Read the source before you install it.

Installation

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

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.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/getcrew44/crew44/tree/main/daemon/internal/presets/defaultcrew/skills/designer/accessibility-review
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/getcrew44/crew44/tree/main/daemon/internal/presets/defaultcrew/skills/designer/accessibility-review

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

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/getcrew44/crew44.git /tmp/crew44
mkdir -p .claude/skills
cp -r /tmp/crew44/daemon/internal/presets/defaultcrew/skills/designer/accessibility-review .claude/skills/accessibility-review

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Accessibility Review 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 Review 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 Review 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 Review

Catch the issues that block users before they reach engineering. Most accessibility failures are predictable from the design alone.

WCAG 2.1 AA quick reference

Perceivable

1.1.1 — Non-text content has alt text.
1.3.1 — Structure and meaning conveyed semantically, not visually.
1.4.3 — Contrast ≥ 4.5:1 for body text, ≥ 3:1 for large text (18px+).
1.4.11 — Non-text contrast ≥ 3:1 for UI components and meaningful graphics.

Operable

2.1.1 — All functionality available by keyboard.
2.4.3 — Logical focus order matches the visible reading order.
2.4.7 — Focus indicator is visible and not hidden by outline: none.
2.5.5 — Touch target ≥ 44×44 CSS pixels.

Understandable

3.2.1 — Predictable on focus; no unexpected context changes.
3.3.1 — Errors are identified clearly and tied to the failing field.
3.3.2 — Inputs have visible labels or instructions, not just placeholders.

Robust

4.1.2 — Every interactive control has a name, role, and value exposed to assistive tech.

Common issues to look for first

Insufficient color contrast — especially gray-on-white body text and brand-color CTAs.
Form fields with placeholder-as-label (placeholder disappears on focus).
Click targets under 44×44.
Focus indicators removed in CSS without a replacement.
Modals that trap focus incorrectly (or don't trap at all).
Color used as the only signal (red text alone for errors, green-only success).
Icon-only buttons with no accessible name.
Auto-playing media with no pause control.

Testing approach

Automated contrast and structure scan first (catches the easy wins).
Walk the screen by keyboard only. Tab, Shift+Tab, Enter, Space, Escape, arrow keys.
Screen reader pass (VoiceOver or NVDA). Listen to how each element announces.
Zoom to 200%. Does the layout break? Does anything become unreachable?

Output

Summary — total issues, count by severity (critical / major / minor).
Findings — grouped by WCAG principle (Perceivable / Operable / Understandable / Robust). Each finding: element, issue, WCAG criterion, severity, recommended fix.
Color contrast check — table of body text, secondary text, UI elements, with foreground/background/ratio/pass.
Keyboard walkthrough — note any element that cannot be reached, activated, or escaped via keyboard.
Priority fixes — top three, each named with who it blocks and what it unblocks.

Anti-patterns

Treating accessibility as a final polish pass instead of a design constraint.
Citing the WCAG number without explaining the user impact.
Generic "improve contrast" — name the specific element, the current ratio, the required ratio.
Ignoring screen reader experience because the visual passes.

Frequently asked questions

What does the Accessibility Review AI skill do?

Use to audit a design or page for WCAG 2.1 AA — contrast, keyboard, focus, labels, touch targets, screen reader behavior.

Why use Accessibility Review on TypingMind?

Because you install it once and use it with any model. Accessibility Review 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 Review in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/getcrew44/crew44/tree/main/daemon/internal/presets/defaultcrew/skills/designer/accessibility-review. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Accessibility Review?

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 Review?

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

Is the Accessibility Review AI skill free?

Yes. It is published on GitHub by getcrew44 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

Pretext

NousResearch

OrganizationPopular

Build creative browser demos with DOM-free text layout.

Sketch

Throwaway HTML mockups: 2-3 design variants to compare.

Tldraw Offline

Drive and script tldraw offline canvases with an agent.

Brand Guidelines

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…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Accessibility Review

WCAG 2.1 AA quick reference

Common issues to look for first

Testing approach

Output

Anti-patterns

Frequently asked questions

Related AI Skills

Set up your own AI workspace now