agentleFS
Sign inStart free
mzeleniukmzeleniuk/ClaudeVueProjectTemplate/.claude/skills/accessibility-audit/SKILL.md

accessibility-audit

Skill0 starsChanged 7 months agoMITView on GitHub

Audit Vue 3 components and pages for accessibility issues: semantic HTML, ARIA roles and attributes, keyboard navigation, focus management, dynamic content announcements, and color contrast (CSS custom properties). Use when the user mentions a11y, accessibility, screen readers, keyboard navigation, WCAG, or when preparing for a production or compliance 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 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

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

  • 0

    Common

    Most of the 46 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 9

    Very specific

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

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

    Check that headings are hierarchical (h1 → h2 → h3), not skipped.

    line 19
  2. Very specific:

    Verify form inputs are wrapped in <label> or linked via for / aria-labelledby.

    line 20
  3. Very specific:

    Check that aria-label or aria-labelledby is present on icon-only buttons.

    line 24
  4. Very specific:

    Verify aria-expanded, aria-controls, and aria-haspopup are toggled correctly in dropdowns and modals.

    line 25
  5. Distinctive:

    Check that modals and dialogs implement a focus trap (focus cycles inside while open.

    line 31
  6. Very specific:

    Verify @keydown.esc closes overlays.

    line 33
  7. Very specific:

    Look for content that updates without a page navigation — these need an aria-live region (polite for status messages, assertive for errors).

    line 36
  8. Very specific:

    Check that loading states have aria-busy="true" and an accessible label.

    line 38
  9. Very specific:

    Verify decorative SVG icons have aria-hidden="true".

    line 42
  10. Very specific:

    Check src/assets/ for CSS custom property definitions.

    line 46

“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

Audit steps

  1. Semantic HTML in templates
    • Grep src/components/ and src/pages/ for <div @click and <span @click that should be <button> or <a>.
    • Check that headings are hierarchical (h1 → h2 → h3), not skipped.
    • Verify form inputs are wrapped in <label> or linked via for / aria-labelledby.
  2. ARIA usage
    • Flag role attributes that duplicate native semantics (e.g., <button role="button">).
    • Check that aria-label or aria-labelledby is present on icon-only buttons.
    • Verify aria-expanded, aria-controls, and aria-haspopup are toggled correctly in dropdowns and modals.
  3. Keyboard navigation
    • Confirm interactive elements are reachable via Tab (no tabindex="-1" on focusable controls except intentional focus traps).
    • Check that modals and dialogs implement a focus trap (focus cycles inside while open; returns to trigger on close).
    • Verify @keydown.esc closes overlays.
  4. Dynamic content
    • Look for content that updates without a page navigation — these need an aria-live region (polite for status messages, assertive for errors).
    • Check that loading states have aria-busy="true" and an accessible label.
  5. Images and icons
    • Grep for <img missing alt attributes.
    • Verify decorative SVG icons have aria-hidden="true".
    • Confirm meaningful icons (standalone buttons) have aria-label.
  6. Color and contrast (CSS layer)
    • Check src/assets/ for CSS custom property definitions.
    • Flag any hardcoded hex/rgb color values in <style scoped> blocks that bypass the theming system — these are untestable for contrast at a glance.

Output format

Group findings by component file, then by category:

  • 🔴 Blocker — fails WCAG 2.1 AA (keyboard trap, missing alt, no label)
  • 🟡 Warning — degrades experience for assistive technology users
  • 🟢 Enhancement — WCAG AAA or UX improvement

For WCAG criteria mapping, see WCAG-QUICK-REF.md.

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