Check Accessibility logo

Check Accessibility

Organization
AgnosticUI
check-accessibility

Review component for accessibility issues

Overview

PublisherAgnosticUI
Repositoryagnosticui
Skill namecheck-accessibility
Stars
832
Forks
47
Bundled files
Instructions only
LicenseApache-2.0
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 AgnosticUI on GitHub. Read the source before you install it.

Installation

Install the Check Accessibility 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/AgnosticUI/agnosticui/tree/master/.claude/skills/check-accessibility
  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/AgnosticUI/agnosticui.git /tmp/agnosticui
mkdir -p .claude/skills
cp -r /tmp/agnosticui/.claude/skills/check-accessibility .claude/skills/check-accessibility
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

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

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:

  1. Read .claude/PROJECT_CONTEXT.md for AgnosticUI structure and accessibility principles

Process:

  1. 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
  2. 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
  3. 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
  4. 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
  5. 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
  6. 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

Frequently asked questions

What does the Check Accessibility AI skill do?

Review component for accessibility issues

Why use Check Accessibility on TypingMind?

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

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/AgnosticUI/agnosticui/tree/master/.claude/skills/check-accessibility. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Check Accessibility?

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

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

Is the Check Accessibility AI skill free?

Yes. It is published on GitHub by AgnosticUI under the Apache-2.0 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 👇