Accessibility Testing

Community

aj-geddes

accessibility-testing

Test web applications for WCAG compliance and ensure usability for users with disabilities. Use for accessibility test, a11y, axe, ARIA, keyboard navigation, screen reader compatibility, and WCAG validation.

Overview

Publisher	aj-geddes
Repository	`useful-ai-prompts`
Skill name	`accessibility-testing`
Stars	340
Forks	55
Bundled files	8
License	MIT
Links	Skill source Repository

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.
8 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by aj-geddes on GitHub. Read the source before you install it.

Installation

Install the Accessibility Testing 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.
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/aj-geddes/useful-ai-prompts.git /tmp/useful-ai-prompts
mkdir -p .claude/skills
cp -r /tmp/useful-ai-prompts/skills/accessibility-testing .claude/skills/accessibility-testing

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

Use it in TypingMind

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

Overview

Accessibility testing ensures web applications are usable by people with disabilities, including those using screen readers, keyboard navigation, or other assistive technologies. It validates compliance with WCAG (Web Content Accessibility Guidelines) and identifies barriers to accessibility.

When to Use

Validating WCAG 2.1/2.2 compliance
Testing keyboard navigation
Verifying screen reader compatibility
Testing color contrast ratios
Validating ARIA attributes
Testing form accessibility
Ensuring focus management
Testing with assistive technologies

Quick Start

Minimal working example:

typescript
// tests/accessibility/homepage.a11y.test.ts
import { test, expect } from "@playwright/test";
import AxeBuilder from "@axe-core/playwright";

test.describe("Homepage Accessibility", () => {
  test("should not have any automatically detectable WCAG A or AA violations", async ({
    page,
  }) => {
    await page.goto("/");

    const accessibilityScanResults = await new AxeBuilder({ page })
      .withTags(["wcag2a", "wcag2aa", "wcag21a", "wcag21aa"])
      .analyze();

    expect(accessibilityScanResults.violations).toEqual([]);
  });

  test("navigation should be accessible", async ({ page }) => {
    await page.goto("/");

    const results = await new AxeBuilder({ page }).include("nav").analyze();

    expect(results.violations).toEqual([]);
  });

// ... (see reference guides for full implementation)

Reference Guides

Detailed implementations in the references/ directory:

Guide	Contents
axe-core with Playwright	axe-core with Playwright
Keyboard Navigation Testing	Keyboard Navigation Testing
ARIA Testing	ARIA Testing
Jest with jest-axe	Jest with jest-axe
Cypress Accessibility Testing	Cypress Accessibility Testing
Python with Selenium and axe	Python with Selenium and axe

Best Practices

✅ DO

Test with real assistive technologies
Include keyboard-only users
Test color contrast
Use semantic HTML
Provide text alternatives
Test with screen readers
Run automated tests in CI
Follow WCAG 2.1 AA standards

❌ DON'T

Rely only on automated tests (they catch ~30-40% of issues)
Use color alone to convey information
Skip keyboard navigation testing
Forget focus management in dynamic content
Use div/span for interactive elements
Hide focusable content with display:none
Ignore ARIA best practices
Skip manual testing

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Accessibility Testing AI skill do?

Why use Accessibility Testing on TypingMind?

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

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/aj-geddes/useful-ai-prompts/tree/main/skills/accessibility-testing. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Accessibility Testing?

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

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

Is the Accessibility Testing AI skill free?

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

Skill Creator

anthropics

OrganizationPopular

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a…

Next Cache Components Adoption

vercel

OrganizationPopular

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the `cacheComponents` flag, work…

Next Cache Components Optimizer

vercel

OrganizationPopular

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal…

Next Partial Prefetching Adoption

vercel

OrganizationPopular

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the `partialPrefetching` flag, opt routes…

Accessibility Testing

Overview