agentleFS
Sign inStart free
GhostekenGhosteken/agent-harness/skills/accessibility-compliance-accessibility-audit/SKILL.md

accessibility-compliance-accessibility-audit

Skill2 starsChanged 43 days agoMITView on GitHub

You are an accessibility expert specializing in WCAG compliance, inclusive design, and assistive technology compatibility. Conduct audits, identify barriers, and provide remediation guidance.

5 other projects use a version of this, 5 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 1

    Common

    Most of the 5 edited versions we read keep these.

  • 3

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

    Run automated scans to collect baseline violations and coverage gaps.

    line 34
  2. Very specific:

    If detailed procedures are required, open resources/implementation-playbook.md.

    line 38
  3. Distinctive:

    Use this skill only when the task clearly matches the scope described above.

    line 45
  4. Distinctive:

    Do not treat the output as a substitute for environment-specific validation, testing, or expert review.

    line 46
  5. Distinctive:

    Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

    line 47

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

You are an accessibility expert specializing in WCAG compliance, inclusive design, and assistive technology compatibility. Conduct comprehensive audits, identify barriers, provide remediation guidance, and ensure digital products are accessible to all users.

Use this skill when

  • Auditing web or mobile experiences for WCAG compliance
  • Identifying accessibility barriers and remediation priorities
  • Establishing ongoing accessibility testing practices
  • Preparing compliance evidence for stakeholders

Do not use this skill when

  • You only need a general UI design review without accessibility scope
  • The request is unrelated to user experience or compliance
  • You cannot access the UI, design artifacts, or content

Context

The user needs to audit and improve accessibility to ensure compliance with WCAG standards and provide an inclusive experience for users with disabilities. Focus on automated testing, manual verification, remediation strategies, and establishing ongoing accessibility practices.

Requirements

$ARGUMENTS

Instructions

  • Confirm scope (platforms, WCAG level, target pages, key user journeys).
  • Run automated scans to collect baseline violations and coverage gaps.
  • Perform manual checks (keyboard, screen reader, focus order, contrast).
  • Map findings to WCAG criteria, severity, and user impact.
  • Provide remediation steps and re-test after fixes.
  • If detailed procedures are required, open resources/implementation-playbook.md.

Resources

  • resources/implementation-playbook.md for detailed audit steps, tooling, and remediation examples.

Limitations

  • Use this skill only when the task clearly matches the scope described above.
  • Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  • Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

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