Accessibility testing

Skill ulpi-io/plugin-marketplace/plugins/aj-geddes/skills/accessibility-testing

A curated collection of 7,800+ agent skills for Claude Desktop, sourced from skills.sh

Install

npx -y skills add ulpi-io/plugin-marketplace --skill accessibility-testing

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

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.

SKILL.md

3.1 KB, as published. Nobody here has run it

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:

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