agentleFS
gologo13gologo13/agent-skills/skills/accessibility-audit/SKILL.md

accessibility-audit

Skill0 starsChanged 9 months agoMITView on GitHub

Perform comprehensive accessibility (a11y) audit of the current UI code to ensure compliance...; keywords: wcag, accessibility, review, test. Use only on explicit request; skip in routine implementation discussions.

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 43 edited versions we read keep these.

  • 10

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Check conformance to WCAG 2.1 guidelines (A, AA, AAA levels)

    line 15
  2. Distinctive:

    Verify proper semantic HTML structure

    line 16
  3. Distinctive:

    Ensure keyboard navigation support

    line 17
  4. Distinctive:

    Check heading hierarchy and structure

    line 21
  5. Distinctive:

    Ensure form labels and error messages are accessible

    line 22
  6. Distinctive:

    Verify focus management and visible focus indicators

    line 25
  7. Distinctive:

    Check tab order and keyboard shortcuts

    line 26
  8. Distinctive:

    Ensure interactive elements are properly sized

    line 27
  9. Distinctive:

    Create accessibility test cases

    line 32
  10. Distinctive:

    Create accessible component patterns

    line 38

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

Perform comprehensive accessibility (a11y) audit of the current UI code to ensure compliance with WCAG guidelines and provide an inclusive user experience.

Steps

  1. WCAG Compliance
    • Check conformance to WCAG 2.1 guidelines (A, AA, AAA levels)
    • Verify proper semantic HTML structure
    • Ensure keyboard navigation support
    • Review color contrast and visual accessibility
  2. Screen Reader Support
    • Validate ARIA labels and descriptions
    • Check heading hierarchy and structure
    • Ensure form labels and error messages are accessible
    • Review dynamic content announcements
  3. Interactive Elements
    • Verify focus management and visible focus indicators
    • Check tab order and keyboard shortcuts
    • Ensure interactive elements are properly sized
    • Review modal and dialog accessibility
  4. Testing & Tools
    • Suggest automated accessibility testing tools
    • Provide manual testing procedures
    • Create accessibility test cases
    • Recommend browser extensions and validators
  5. Remediation
    • Provide specific code fixes for each issue
    • Include ARIA attributes and semantic improvements
    • Suggest alternative approaches for complex interactions
    • Create accessible component patterns

Accessibility Audit Checklist

  • WCAG compliance verified
  • Screen reader support validated
  • Interactive elements accessible
  • Testing tools recommended
  • Remediation code provided with examples

Download now (ZIP)

  • Other versions51 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 1

    1. emaraschio/cursor-commands★ 973% same

    Wrote their own version · 50

    1. me2resh/apexyard★ 532same name
    2. github/replica★ 117same name
    3. cuellarfr/design-skills★ 94same name
    4. adityareddy-dev/deskstudio★ 42same name
    5. launchapp-dev/animus-cli★ 39same name
    6. kumaran-is/claude-code-onboarding★ 35same name
    7. 5throck/ai-workspace-standards★ 23same name
    8. Indium-AI-Labs/indium-agentkit★ 18same name
    9. Ionate-Technologies/indium-agentkit★ 17same name
    10. brayandiazc/project-starter-template-es-ai★ 15same name

    40 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use design-system-audit, observability-setup 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

    • 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

    • AnthropicSkill

      design-critique

      Get structured design feedback on usability, hierarchy, and consistency. Trigger with "review this design", "critique this mockup", "what do you think of this screen?", or when sharing a Figma link or screenshot for feedback at any stage from exploration to final polish.

      Also in 4 projects that use this

    • ilikescienceSkill

      design-tokens

      Expert in design tokens using the DTCG specification. Use this skill when users ask about design tokens, DTCG format, token validation, formatting, transformation, color spaces (sRGB, Display P3, OKLCH), references and aliasing, resolvers, theming with modifiers/contexts, multi-platform design systems, accessibility, or working with tools like jq, jsonata, and terrazzo. Helps with token file creation, resolver configuration, structure, naming conventions, and best practices.

      Also in 3 projects that use this

    • francogalfreSkill

      dependency-audit

      Audits package.json dependencies for outdated packages, security vulnerabilities, unnecessary deps, and version issues. Use when the user says "audit my dependencies", "check my packages", "what deps should I update", "clean up package.json", "are there security issues in my deps", or pastes a package.json.

      Also in 3 projects that use this

    • OpenAISkill

      threat-model

      Use when Codex is already in the threat-modeling phase of a security scan, the user explicitly invokes $threat-model, or the user explicitly asks to create, update, or persist a repository threat model. Do not use as the primary trigger for full PR, commit, branch, patch, or repository scans.

      Also in 3 projects that use this

  • In this repository31 other files it gives its agents.

Does it work?

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

Reviews can't be read right now.

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.