agentleFS
Sign inStart free
emaraschioemaraschio/cursor-commands/.cursor/skill-contracts/accessibility-audit/SKILL.md

accessibility-audit

Skill9 starsChanged 3 months agoMITView on GitHub

Audit UI for WCAG accessibility issues and fixes

55 other projects use a version of this, 1 of them edited.

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

Show its rules and text

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 46 edited versions we read keep these.

  • 13

    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
  • could be automatic: a setting could enforce it
  1. Distinctive:

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

    line 13
  2. Distinctive:

    Verify proper semantic HTML structure

    line 14
  3. Distinctive:

    Ensure keyboard navigation support

    line 15
  4. Distinctive:

    Check heading hierarchy and structure

    line 19
  5. Distinctive:

    Ensure form labels and error messages are accessible

    line 20
  6. Distinctive:

    Verify focus management and visible focus indicators

    line 23
  7. Distinctive:

    Check tab order and keyboard shortcuts

    line 24
  8. Distinctive:

    Ensure interactive elements are properly sized

    line 25
  9. Distinctive:

    Create accessibility test cases

    line 30
  10. Distinctive:

    Create accessible component patterns

    line 36
  11. Distinctive:

    Verify keyboard navigation and screen reader behavior, not only automated scans.

    line 49
  12. Distinctive:

    Do not print or commit secrets, tokens, or credentials found while auditing UI code.

    line 50
  13. Distinctive:

    Do not commit, push, or merge changes without explicit consent.

    line 51

“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

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

Guardrails

  • Change only accessibility issues; do not touch unrelated code.
  • Verify keyboard navigation and screen reader behavior, not only automated scans.
  • Do not print or commit secrets, tokens, or credentials found while auditing UI code; flag their location instead.
  • Do not commit, push, or merge changes without explicit consent.

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