Accessibility Check

Community

dev-ik

accessibility-check

Use when implemented interactive UI needs practical checks of keyboard navigation, visible focus, accessible names, form labels and errors, dialog focus, touch targets, color-only status, or reduced motion. Skip legal certification and backend-only work.

Overview

Publisher	dev-ik
Repository	`ai-design-rules`
Skill name	`accessibility-check`
Stars	3
Forks	0
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 dev-ik on GitHub. Read the source before you install it.

Installation

Install the Accessibility Check 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/dev-ik/ai-design-rules/tree/main/skills/accessibility-check
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.

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-check .claude/skills/accessibility-check

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

Use it in TypingMind

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

Exercise the user's flow and inspect semantics as well as pixels. This execution skill complements accessibility-reviewer; it is not a conformance certificate.

Retrieve matching graph context and read applicable research, particularly A11Y-001 through A11Y-004. Record the actual browser, viewport, data, states, and tools. If only source or a screenshot is available, identify that limited scope and mark behavioral checks unverified.

Check the implemented flow

Inspect semantic elements and accessible names. Buttons perform actions; links navigate. Inputs have associated labels. Icon-only controls have meaningful names or decorative icons are hidden. Prefer native elements; inspect existing custom controls without adding unnecessary ARIA.
Use keyboard input to follow the primary journey. Check Tab and Shift+Tab order, visible focus, Enter/Space where relevant, and access to actions that also work with a pointer. For dialogs and sheets, observe initial focus, containment when modal, Escape behavior where supported, and focus restoration after closing. A role locator alone does not establish keyboard behavior.
Trigger input errors and recovery. Observe specific textual messages, association with the affected input, retained values, and retry. Check applicable loading, success, and disabled states for understandable feedback and remaining navigation.
Measure clickable target bounds, not just visible icons, when applying the graph's A11Y-001. Inspect responsive collision risks with responsive-check.
Inspect focus and status in screenshots. For contrast, use actual foreground/background values and a suitable measurement tool; a visual impression cannot prove a numeric contrast ratio. State the applicable criterion and report unknown composite/translucent colors as unresolved. Status must remain understandable without color alone.
When interaction motion exists, exercise the available reduced-motion preference and confirm equivalent function and feedback. Record any assistive-technology testing actually performed; browser DOM/role inspection does not prove screen-reader behavior.

For authorized fixes, preserve business logic, use the existing component system, and repeat the failed keyboard/error/state interaction. Capture focused evidence before and after where visible behavior is involved.

Output

Return scoped verdict | tools and conditions | confirmed findings | coverage gaps. A finding includes severity, affected control/state, keyboard or pointer reproduction, measured/observed evidence, user impact, applicable graph rule or external criterion, fix, verified component/file, and retest status. Distinguish checked, unverified, and not applicable for labels/semantics, keyboard/focus, dialogs, errors/recovery, targets, contrast, reduced motion, and assistive technology. Missing evidence is not a pass or a confirmed implementation defect.

Sources: CHECK-00001, RULE-00009 through RULE-00013, research/accessibility/textual-error-recovery.md, and research/accessibility/keyboard-focus-and-interaction-motion.md. Playwright role and label locators provide useful semantic feedback but do not replace accessibility audits.

Frequently asked questions

What does the Accessibility Check AI skill do?

Why use Accessibility Check on TypingMind?

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

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

Which AI models can use Accessibility Check?

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

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

Is the Accessibility Check 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

Openclaw Qa Testing

openclaw

OrganizationPopular

Run, watch, debug, extend, or explain OpenClaw qa-lab and qa-channel scenarios, artifacts, and live lanes.

Proof Video

Add subtitles, captions, narration cues, or zoom to a proof video or PR recording using repo-local capture helpers and a system ffmpeg renderer.

Slack E2e

Test Slack with Convex-leased user OAuth or QA bots; check credentials, exercise owned messages, prove Gateway behavior, and distinguish API evidence from real Slack client interactions.

Telegram E2e Userbot

Prove user-visible OpenClaw Telegram behavior on Telegram's Test Server with Convex-leased team credentials; drive real-user turns and record messages, edits, deletions, reactions, typing, or rich…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Accessibility Check

Check the implemented flow

Output

Frequently asked questions

Related AI Skills

Set up your own AI workspace now