agentleFS
Sign inStart free
luigi-dvluigi-dv/react-ts-vite/.claude/skills/accessibility-audit/SKILL.md

accessibility-audit

Skill1 starsChanged 27 days agoMITView on GitHub

Audit and fix the accessibility of pages and components built with Tailwind, Headless UI and Heroicons — semantics, headings, names, keyboard, focus, contrast, forms, live regions, motion — and verify with Testing Library queries. Use when asked about a11y, WCAG, screen readers, keyboard support or when reviewing UI changes.

55 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use design-system-audit, flaky-test-triage and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • jpoindexterSkill

    design-system-audit

    Audit code for design system violations - grid spacing, tokens, existing components

    Also in 4 projects that use this

  • SUDARSHANCHAUDHARISkill

    flaky-test-triage

    Diagnoses inconsistent test results by separating product nondeterminism, automation defects, shared data, timing, infrastructure, environment, order, and concurrency effects.

    Also in 3 projects that use this

  • tekumaraSkill

    api-design-review

    Reviews REST API design by inventorying routes, finding overlapping functionality, comparing payloads and pagination, and checking resource naming, URL structure, identifiers, errors, idempotency, and timestamps. Use when asked to review API routes, compare endpoints, find redundant or superseding operations, assess contract consistency, or run a REST API design review.

    Also in 3 projects that use this

  • BufferoverflovvSkill

    observability-setup

    Add production observability to a FastMCP server: request IDs, slow-request logging, structured log fields, and optional Prometheus metrics. Use when: hardening logging for production, adding request tracing or correlation IDs, setting up slow-request alerts, adding a /metrics endpoint, or improving structured log output beyond the base middleware.

    Also in 3 projects that use this

  • mmondoraSkill

    infrastructure-as-code

    Infrastructure as Code with Terraform and Pulumi. State management, modularity, drift detection, secrets handling. Use when provisioning cloud resources, writing Terraform/Pulumi modules, or managing infrastructure configuration.

    Also in 3 projects that use this

  • OpenAISkill

    design-qa

    Internal prototype QA helper. Use only after a Product Design prototype, URL-to-code build, or image-to-code build has a source visual target and a rendered implementation to compare before handoff. Do not use for broad UX critique, design critique, product audits, or flow reviews; route those user-facing requests to audit.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 46 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If a query needs data-testid, the markup probably lacks semantics — fix the markup first.

    line 36

“Common” is measured: kept by at least 6 in 10 of the 46 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Accessibility audit

Target: WCAG 2.2 AA. Work through the checklist on the rendered page (dev server) and the source.

Checklist

  1. Landmarks & structure — header, nav (with aria-label when more than one), main, footer; exactly one h1; headings in order without skipping levels; lists are ul/ol.
  2. Names — every control has an accessible name: visible text, <label htmlFor>, or sr-only text for icon-only buttons; images have alt (empty for decoration); icons aria-hidden="true".
  3. Keyboard — everything reachable with Tab in a sensible order; Enter/Space activate; Escape closes dialogs/menus (Headless UI handles this when you use its components); no keyboard traps; skip link for long pages (sr-only focus:not-sr-only).
  4. Focus — visible focus on every interactive element (focus-visible:outline focus-visible:outline-2 focus-visible:outline-offset-2 focus-visible:outline-brand-600); focus moves into dialogs and returns on close (Headless UI); never outline-none without a replacement.
  5. Contrast — text ≥ 4.5:1, large text/UI ≥ 3:1. The default brand scale: brand-600 on white and brand-400 on gray-900 pass; check custom palettes with a contrast checker. Do not convey state by colour alone (add icon or text).
  6. Forms — visible labels, autoComplete, type, errors linked via aria-describedby + aria-invalid, submit feedback in role="status"/aria-live="polite", required fields marked in text.
  7. Dynamic content — loading and result announcements through live regions; dialogs via Dialog with DialogTitle; menus via Menu; current page via aria-current="page".
  8. Motion & preferences — respect prefers-reduced-motion (motion-safe:/motion-reduce:), dark mode via dark:; no auto-playing media.
  9. Responsive & zoom — no horizontal scroll at 320 px; text resizes to 200 %; touch targets ≥ 24 px.
  10. Language & titles — <html lang>, meaningful <title> per page.

Verify with tests

screen.getByRole('heading', { level: 1 })
screen.getByRole('button', { name: /open main menu/i })
screen.getByLabelText('Email address')
expect(screen.getByRole('status')).toHaveTextContent(/saved/i)

If a query needs data-testid, the markup probably lacks semantics — fix the markup first. For automated checks add vitest-axe or run Lighthouse/axe DevTools in the browser.

Report format

For each issue: location, WCAG criterion (e.g. 1.3.1, 2.4.7, 4.1.2), impact (blocker / serious / moderate / minor), fix with the exact Tailwind/JSX change.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free