agentleFS
TheGoat395TheGoat395/Codex-Skills/skills/accessibility-audit-websites/SKILL.md

accessibility-audit-websites

Skill136 starsChanged 5 months agoMITView on GitHub

Audit semantic and keyboard accessibility.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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:

    Use this skill to make sites usable for more people and prevent polished visuals from hiding broken interaction.

    line 8
  2. Distinctive:

    Read Accessibility Audit Websites Guide before claiming the site is ready.

    line 13

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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 Websites

Use this skill to make sites usable for more people and prevent polished visuals from hiding broken interaction.

Workflow

  1. Inspect the affected surface, relevant project scripts, target URL and available inspection tooling; reuse existing context.
  2. Read Accessibility Audit Websites Guide before claiming the site is ready.
  3. Sample the affected keyboard journeys, accessible names and states, form errors, focus visibility, and media alternatives. Include open, invalid and loading states where those change accessibility; an automated scan alone is insufficient.
  4. Fix issues when they are in scope; otherwise record exact evidence and remaining risk.
  5. Summarize commands, URLs, screenshots/checks, changed files, and what was not tested.

Scoped execution

Apply the shared web contract once when execution crosses phases; reuse it if already read. Load only the specialist guidance relevant to the requested surface and deliverable.

Scope and evidence

Report the audited surfaces, manual keyboard/accessibility checks, sampled coverage and unassessed areas. Sampled success does not establish whole-site WCAG conformance.

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.