agentleFS
Sign inStart free
aprameyakaprameyak/coding-skills/accessibility/SKILL.md

accessibility

Skill1 starsChanged 41 days agoMITView on GitHub

Audit and fix UI accessibility issues. Use when building UI, reviewing frontends, or when the user asks for a11y/WCAG work.

123 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use author-contributions, tool-rename-deprecation 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.
  • MicrosoftSkill

    author-contributions

    Identify all files a specific author contributed to on a branch vs its upstream, tracing code through renames. Use when asked who edited what, what code an author contributed, or to audit authorship before a merge. This skill should be run as a subagent — it performs many git operations and returns a concise table.

    Also in 7 projects that use this

  • gitpod-ioSkill

    tool-rename-deprecation

    Ensure renamed built-in tool references preserve backward compatibility. Use when renaming a toolReferenceName, tool set referenceName, or any tool identifier. Run on ANY change to tool registration code. Covers legacyToolReferenceFullNames for tools and legacyFullNames for tool sets.

    Also in 5 projects that use this

  • DepressionCenterSkill

    project-preferences

    Apply repository-specific preferences when planning, implementing, or reviewing changes in this project.

    Also in 6 projects that use this

  • MicrosoftSkill

    chat-perf

    Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

    Also in 5 projects that use this

  • DepressionCenterSkill

    create-media-pack

    Create a coordinated project branding and media pack with three accessible design options, approved vector artwork, image exports, a branding guide, and README integration. Use when asked for a repository media pack, brand kit, or complete project visual identity.

    Also in 5 projects that use this

  • +7 more from microsoft

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 112 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. Distinctive:

    Check names/roles with accessibility tree tooling when available.

    line 22
  2. Distinctive:

    Add regression coverage for critical flows when the stack supports it.

    line 24
  3. Very specific:

    Prefer native elements (button, a, label, input) over clickable divs.

    line 28
  4. Distinctive:

    Do not disable focus outlines without a better visible replacement.

    line 29

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

Checklist

  • Keyboard reachability and visible focus for interactive controls
  • Semantic HTML before ARIA; correct roles/names/states when ARIA is needed
  • Form inputs have labels; errors are announced
  • Images have appropriate alt text (or empty alt if decorative)
  • Color is not the only signal; contrast meets target
  • Hit targets are usable on touch
  • Motion respects reduced-motion preferences when adding animation
  • Dialogs/menus manage focus and dismissal

Process

  1. Walk the changed UI with keyboard only.
  2. Check names/roles with accessibility tree tooling when available.
  3. Fix root markup before adding ARIA patches.
  4. Add regression coverage for critical flows when the stack supports it.

Rules

  • Prefer native elements (button, a, label, input) over clickable divs.
  • Do not disable focus outlines without a better visible replacement.

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