agentleFS
GhostekenGhosteken/agent-harness/skills/wcag-audit-patterns/SKILL.md

wcag-audit-patterns

Skill2 starsChanged 43 days agoMITView on GitHub

Comprehensive guide to auditing web content against WCAG 2.2 guidelines with actionable remediation strategies.

9 other projects use a version of this, 6 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 3

    Common

    Most of the 3 edited versions we read keep these.

  • 3

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

    Run automated scans (axe, Lighthouse, WAVE) to collect initial findings.

    line 27
  2. Common:

    Avoid claiming legal compliance without expert review.

    line 36
  3. Common:

    Keep evidence of test steps and results for audit trails.

    line 37
  4. Distinctive:

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

    line 44
  5. Distinctive:

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

    line 45
  6. Distinctive:

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

    line 46

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

WCAG Audit Patterns

Comprehensive guide to auditing web content against WCAG 2.2 guidelines with actionable remediation strategies.

Use this skill when

  • Conducting accessibility audits
  • Fixing WCAG violations
  • Implementing accessible components
  • Preparing for accessibility lawsuits
  • Meeting ADA/Section 508 requirements
  • Achieving VPAT compliance

Do not use this skill when

  • You need legal advice or formal certification
  • You only want a quick automated scan without manual verification
  • You cannot access the UI or source for remediation work

Instructions

  1. Run automated scans (axe, Lighthouse, WAVE) to collect initial findings.
  2. Perform manual checks (keyboard navigation, focus order, screen reader flows).
  3. Map each issue to a WCAG criterion, severity, and remediation guidance.
  4. Re-test after fixes and document residual risk and compliance status.

Refer to resources/implementation-playbook.md for detailed patterns, checklists, and templates.

Safety

  • Avoid claiming legal compliance without expert review.
  • Keep evidence of test steps and results for audit trails.

Resources

  • resources/implementation-playbook.md for detailed patterns, checklists, and templates.

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.