agentsclimarketplace

Accessibility automation expert

Skill curiositech/windags-skills/skills/accessibility-automation-expert

Implement WCAG 2.2 AA/AAA compliance with automated testing, keyboard navigation, screen reader support, and focus management. Activate on: accessibility audit, WCAG compliance, keyboard navigation, screen reader, aria attributes, axe-core, focus trap. NOT for: design-level accessibility review (use design-accessibility-auditor), color contrast only (use css-in-js-architect).From its SKILL.md

Install
npx -y skills add curiositech/windags-skills --skill accessibility-automation-expert

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.
  • 18 stars18 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 file declares

Copied from the file, not written here

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

9.1 KB, as published. Nobody here has run it

Accessibility Automation Expert

Implement and enforce WCAG 2.2 AA/AAA compliance through automated testing, keyboard navigation, ARIA patterns, screen reader optimization, and focus management.

Activation Triggers

Activate on: accessibility audit failures, WCAG compliance requirements, keyboard navigation broken, screen reader not announcing content, axe-core violations, focus trap for modals/dialogs, aria-* attribute questions, skip navigation links.

NOT for: design-level accessibility review (color choices, layout decisions) -- use design-accessibility-auditor. Pure color contrast checking -- use css-in-js-architect with OKLCH.

Quick Start

  1. Run axe-core -- npx @axe-core/cli http://localhost:3000 or integrate @axe-core/react in dev mode for console warnings.
  2. Fix critical violations first -- missing alt text, missing form labels, insufficient contrast, missing landmarks.
  3. Implement keyboard navigation -- every interactive element must be reachable and operable with Tab, Enter, Space, Escape, and Arrow keys.
  4. Add focus management -- trap focus in modals, restore focus on close, manage focus on route change.
  5. Test with a screen reader -- VoiceOver (macOS), NVDA (Windows), or TalkBack (Android) for real validation.

Core Capabilities

DomainTechnologiesKey Patterns
Automated Testingaxe-core, Lighthouse, jest-axe, Playwright axeCI/CD accessibility gates
Keyboard Navigationtabindex, onKeyDown, roving tabindexArrow key navigation, focus groups
Screen ReadersARIA roles, live regions, aria-labelAnnouncements, state changes, descriptions
Focus Managementfocus-visible, focus trap, inert attributeModal focus lock, skip links, route change focus
Semantic HTML<main>, <nav>, <article>, <aside>Landmarks, heading hierarchy, lists
Forms<label>, aria-describedby, aria-invalidError announcement, required fields, fieldsets

Architecture Patterns

Pattern 1: Automated axe-core in CI

// e2e/accessibility.spec.ts (Playwright + axe-core)
import { test, expect } from '@playwright/test';
import AxeBuilder from '@axe-core/playwright';

const pages = ['/', '/products', '/checkout', '/account'];

for (const path of pages) {
  test(`${path} has no accessibility violations`, async ({ page }) => {
    await page.goto(path);
    await page.waitForLoadState('networkidle');

    const results = await new AxeBuilder({ page })
      .withTags(['wcag2a', 'wcag2aa', 'wcag22aa'])  // WCAG 2.2 AA
      .analyze();

    expect(results.violations).toEqual([]);
  });
}
// Dev mode: axe-core in React (shows violations in console)
// app/layout.tsx
if (process.env.NODE_ENV === 'development') {
  import('@axe-core/react').then((axe) => {
    axe.default(React, ReactDOM, 1000);
  });
}

Pattern 2: Focus Management for Modals

import { useEffect, useRef, useCallback } from 'react';

function useFocusTrap(isOpen: boolean) {
  const containerRef = useRef<HTMLDivElement>(null);
  const previousFocusRef = useRef<HTMLElement | null>(null);

  useEffect(() => {
    if (!isOpen) return;

    // Save current focus to restore later
    previousFocusRef.current = document.activeElement as HTMLElement;

    // Focus first focusable element
    const container = containerRef.current;
    if (!container) return;

    const focusable = container.querySelectorAll<HTMLElement>(
      'a[href], button:not([disabled]), input:not([disabled]), textarea:not([disabled]), select:not([disabled]), [tabindex]:not([tabindex="-1"])'
    );
    focusable[0]?.focus();

    // Trap focus within container
    const handleKeyDown = (e: KeyboardEvent) => {
      if (e.key !== 'Tab') return;
      const first = focusable[0];
      const last = focusable[focusable.length - 1];

      if (e.shiftKey && document.activeElement === first) {
        e.preventDefault();
        last?.focus();
      } else if (!e.shiftKey && document.activeElement === last) {
        e.preventDefault();
        first?.focus();
      }
    };

    container.addEventListener('keydown', handleKeyDown);

    // Use inert on background content
    const mainContent = document.querySelector('main');
    mainContent?.setAttribute('inert', '');

    return () => {
      container.removeEventListener('keydown', handleKeyDown);
      mainContent?.removeAttribute('inert');
      previousFocusRef.current?.focus(); // restore focus
    };
  }, [isOpen]);

  return containerRef;
}

Pattern 3: ARIA Live Regions for Dynamic Content

// Announce form errors, loading states, and updates to screen readers
function useAnnounce() {
  const announce = useCallback((message: string, priority: 'polite' | 'assertive' = 'polite') => {
    const el = document.getElementById(`aria-live-${priority}`);
    if (el) {
      el.textContent = '';  // Clear first to trigger re-announcement
      requestAnimationFrame(() => { el.textContent = message; });
    }
  }, []);

  return announce;
}

// Mount once in layout:
function AriaLiveRegions() {
  return (
    <>
      <div id="aria-live-polite" aria-live="polite" aria-atomic="true" className="sr-only" />
      <div id="aria-live-assertive" aria-live="assertive" aria-atomic="true" className="sr-only" />
    </>
  );
}
  ┌─ Accessibility Testing Pyramid ────────────────────┐
  │                                                     │
  │          ▲  Manual Screen Reader Testing            │
  │         ╱ ╲  (VoiceOver, NVDA — quarterly)         │
  │        ╱───╲                                        │
  │       ╱     ╲  Playwright + axe-core E2E           │
  │      ╱  E2E  ╲  (every page, CI gate)              │
  │     ╱─────────╲                                     │
  │    ╱           ╲  jest-axe Component Tests          │
  │   ╱  Component  ╲  (per interactive component)     │
  │  ╱───────────────╲                                  │
  │ ╱                 ╲  ESLint jsx-a11y                │
  │╱    Static Lint    ╲  (on every commit)             │
  │╲___________________╱                                │
  └─────────────────────────────────────────────────────┘

Anti-Patterns

  1. div with onClick instead of button -- divs have no keyboard interaction, no role, and no focus. Use semantic <button> or <a> elements. If you must use a div, add role="button", tabindex="0", and onKeyDown for Enter/Space.
  2. aria-label on everything -- over-labeling creates noise for screen reader users. Prefer visible text labels; use aria-label only when visible text is impossible.
  3. Hiding focus outlines -- outline: none with no replacement makes keyboard navigation invisible. Use :focus-visible for keyboard-only focus indicators that do not appear on mouse click.
  4. Missing skip navigation link -- keyboard users must tab through the entire nav on every page. Add <a href="#main" class="sr-only focus:not-sr-only">Skip to main content</a> as the first focusable element.
  5. Toast notifications without live regions -- screen readers cannot detect dynamically added toasts. Use aria-live="polite" regions to announce them.

Quality Checklist

  • axe-core CI gate passes with zero violations on all pages
  • eslint-plugin-jsx-a11y enabled with no warnings
  • All images have descriptive alt text (or alt="" for decorative images)
  • All form inputs have associated <label> elements (not just placeholder text)
  • Heading hierarchy is sequential (h1 > h2 > h3, no skipping)
  • Page landmarks present: <main>, <nav>, <header>, <footer>
  • Skip navigation link is the first focusable element
  • Focus visible on all interactive elements (:focus-visible styles defined)
  • Modals trap focus and restore focus on close
  • Dynamic content changes announced via aria-live regions
  • Color contrast ratios meet WCAG AA (4.5:1 normal text, 3:1 large text)
  • All functionality operable with keyboard only (Tab, Enter, Space, Escape, Arrow keys)

Keep looking

Skills are one crate of 611,178. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.