Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
aj-geddes avatar

Accessibility Testing

  • 513 installs
  • 305 repo stars
  • Updated March 4, 2026
  • aj-geddes/useful-ai-prompts

accessibility-testing is a Claude skill from aj-geddes/useful-ai-prompts that runs WCAG audits, keyboard navigation checks, screen reader flows, and remediation plans for web and mobile surfaces before release.

About

accessibility-testing is a Claude skill in aj-geddes/useful-ai-prompts that guides developers through inclusive QA before release. It structures WCAG conformance reviews, keyboard-only navigation checks, screen reader user flows, and actionable remediation plans for web and mobile UI. The skill fits ship-phase testing when compliance, audit readiness, or user inclusivity block a launch. Developers reach for accessibility-testing when a PR needs a11y coverage beyond lint rules, when preparing for WCAG-driven reviews, or when screen reader and keyboard paths have not been validated on real components.

  • WCAG conformance checklist prompts
  • Keyboard and focus order testing
  • Screen reader flow simulation
  • ARIA and semantic HTML review
  • Remediation prioritization by severity

Accessibility Testing by the numbers

  • 513 all-time installs (skills.sh)
  • Ranked #611 of 2,153 Testing & QA skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/aj-geddes/useful-ai-prompts --skill accessibility-testing

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs513
repo stars305
Last updatedMarch 4, 2026
Repositoryaj-geddes/useful-ai-prompts

How do you audit web apps for WCAG compliance?

Run WCAG audits, keyboard navigation checks, screen reader flows, and remediation plans before release so web and mobile surfaces stay inclusive and compliant.

Who is it for?

Frontend and mobile developers preparing release candidates who need structured WCAG, keyboard, and screen reader test coverage.

Skip if: Backend-only API projects with no user interface or teams already running automated axe-core CI with full coverage.

When should I use this skill?

A web or mobile release needs WCAG review, keyboard navigation validation, or screen reader flow testing before launch.

What you get

WCAG audit findings, keyboard navigation reports, screen reader flow results, and remediation plans

  • WCAG audit report
  • remediation plan
  • keyboard flow checklist

Files

SKILL.mdMarkdownGitHub ↗

Accessibility Testing

Table of Contents

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:

// 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:

GuideContents
axe-core with Playwrightaxe-core with Playwright
Keyboard Navigation TestingKeyboard Navigation Testing
ARIA TestingARIA Testing
Jest with jest-axeJest with jest-axe
Cypress Accessibility TestingCypress Accessibility Testing
Python with Selenium and axePython 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

Related skills

How it compares

Pick accessibility-testing for guided a11y QA plans rather than performance profiling or generic unit test generation skills.

FAQ

What checks does accessibility-testing include?

accessibility-testing covers WCAG audits, keyboard navigation checks, screen reader flows, and remediation planning for web and mobile surfaces before release.

When should developers invoke accessibility-testing?

accessibility-testing fits pre-release QA when UI needs WCAG review, keyboard paths are untested, or screen reader flows must be validated before shipping inclusive interfaces.

Testing & QAfrontendtesting

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.