agentleFS
brayandiazcbrayandiazc/project-starter-template-en-ai/.claude/skills/accessibility-audit/SKILL.md

accessibility-audit

Skill2 starsChanged 2 months agoMITView on GitHub

Checks UI changes for accessibility — color contrast, keyboard navigation, focus management, ARIA usage, and alt text. Use this when the user asks for an a11y/accessibility review, to check WCAG compliance, keyboard support, screen-reader friendliness, or focus handling (e.g. "is this modal accessible?", "audit a11y on the form").

58 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use flaky-test-triage, api-design-review and 9 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.
  • 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

  • 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

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

  • 0

    Common

    Most of the 49 edited versions we read keep these.

  • 1

    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 docs/conventions/ contains accessibility or design-system guidance, read it for the project's target standard (e.g.

    line 11
  2. Distinctive:

    Do NOT claim full WCAG conformance from static review alone — flag items that need manual or assistive-tech testing.

    line 23

“Common” is measured: kept by at least 6 in 10 of the 49 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

Audit the named UI for accessibility. Split with design-system-audit: that one covers tokens, primitives, data states and hierarchy; everything about contrast, keyboard, focus and ARIA lives here, in a single list — if the other skill handed you a custom component, this is the list that applies to it.

  1. If docs/conventions/ contains accessibility or design-system guidance, read it for the project's target standard (e.g. WCAG 2.1 AA) and any specific rules.
  2. Locate the UI source in scope and review against these checks:
    • Contrast — text and meaningful UI meet the contrast ratio for their size/role.
    • Keyboard — all interactive elements are reachable and operable by keyboard; no keyboard traps; logical tab order.
    • Focus — visible focus indicators; focus is moved/restored correctly for modals, menus, and route changes.
    • Semantics & ARIA — native elements (button, a, label) preferred; ARIA roles/attributes used correctly and only when needed; form inputs have associated labels.
    • Images & media — alt text on meaningful images, empty alt on decorative ones; captions where relevant.
    • Motion & responsiveness — respects reduced-motion; usable when zoomed/at small sizes.
  3. Report a checklist: each item Pass / Fail / Needs-manual-check, with file:line and a concrete fix.

Example finding: Icon-only button in Nav.tsx:22 has no accessible name — add aria-label.

Do NOT claim full WCAG conformance from static review alone — flag items that need manual or assistive-tech testing.

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.