agentleFS
Sign inStart free
WST2002WST2002/claude-code-skills/skills/accessibility-audit/SKILL.md

accessibility-audit

Skill4 starsChanged 27 days agoMITView on GitHub

Use when checking a website, web app or UI component for accessibility, WCAG or a11y compliance, screen reader or keyboard support, color contrast, ARIA usage, or fixing issues reported by axe, Lighthouse or an accessibility review.

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 8 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

  • 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

  • Sagargupta16Skill

    upgrade-dependencies

    Upgrade a project's dependencies one at a time, running the test suite after each bump and reverting the ones that break it. Use it during routine dependency maintenance, when a batch of updates has accumulated; before a major release, to go into it on current and patched dependencies; when Renovate or Dependabot PRs have piled up and you want them resolved locally in one sitting; when a security advisory means you need the patched version in, and you need to know what it breaks.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 46 edited versions we read keep these.

  • 2

    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. Distinctive:

    Check that everyone can perceive, operate and understand the interface: with a keyboard only, with a screen reader, with zoom, and with low …

    line 10
  2. Very specific:

    Automated scan: if a URL is available: npx @axe-core/cli <url> or Lighthouse accessibility.

    line 14
  3. Distinctive:

    Screen reader semantics: every control has a role, an accessible name and its state (expanded, selected, checked, invalid).

    line 17

“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

Overview

Check that everyone can perceive, operate and understand the interface: with a keyboard only, with a screen reader, with zoom, and with low vision. Fix issues in the components that produce them so the fix applies everywhere they are used.

Method

  1. Automated scan if a URL is available: npx @axe-core/cli <url> or Lighthouse accessibility. Automated tools find about a third of issues; treat results as a starting point.
  2. Code review of components with the checklist below: forms, buttons, links, images, modals, menus, tabs, tables, custom widgets.
  3. Keyboard pass: Tab through every interactive element. Focus visible, logical order, nothing unreachable, no focus traps, Escape closes overlays, focus returns to the trigger.
  4. Screen reader semantics: every control has a role, an accessible name and its state (expanded, selected, checked, invalid).
  5. Report with the contract below, mapped to WCAG 2.2 AA.

Checklist

AreaRequirement (WCAG)
ImagesInformative images have meaningful alt; decorative ones alt="" (1.1.1)
ContrastText 4.5:1, large text and UI components 3:1 (1.4.3, 1.4.11)
ColorInformation not conveyed by color alone (1.4.1)
StructureOne h1, ordered headings, landmarks (header, nav, main, footer), lists as lists (1.3.1)
FormsEvery input has a <label>; errors named in text and linked with aria-describedby; required marked (1.3.1, 3.3.1, 3.3.2)
ControlsActions are <button>, navigation is <a href>; no clickable div without role, tabindex and key handlers (2.1.1, 4.1.2)
FocusVisible focus indicator; never outline: none without a replacement (2.4.7)
Modals and menusFocus moves in, is trapped while open, Escape closes, focus returns (2.1.2, 2.4.3)
NamesIcon-only buttons have aria-label; link text makes sense out of context (2.4.4, 4.1.2)
MotionRespect prefers-reduced-motion; no auto-playing motion longer than 5 s without pause (2.2.2, 2.3.3)
Zoom and reflowUsable at 200% zoom and 320 px width without horizontal scroll (1.4.4, 1.4.10)
TargetsTouch targets at least 24×24 px (2.5.8)
Language<html lang> set (3.1.1)

ARIA rule: prefer native HTML elements. Add ARIA only when no native element fits, and then implement the full keyboard behavior of that pattern.

Output contract

### [Critical | Serious | Moderate | Minor] Title — WCAG <criterion>
- Where: component and file:line (and URL if relevant)
- Who is affected: keyboard users, screen reader users, low vision, etc.
- Fix: corrected markup or CSS

Critical = blocks a task for some users (cannot submit a form by keyboard). End with Passed checks and Needs manual testing (items that require a real screen reader session).

Common mistakes

  • div or span with onClick instead of a button.
  • Placeholder text used as the only label.
  • aria-label that contradicts the visible text.
  • role="button" added without Enter and Space key handling.
  • Claiming WCAG compliance from an automated scan alone.

Made by Wageesha Tripathi · LinkedIn · Email · More skills

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