agentleFS
loganware05loganware05/captains-compass-cursor/.cursor/skills/accessibility-review/SKILL.md

accessibility-review

Skill2 starsChanged 33 days agoMITView on GitHub

Reviews UI changes for keyboard, screen-reader, and inclusive design requirements

17 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use frontend-design.

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.
  • BlockSkill

    frontend-design

    Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, or applications. Generates creative, polished code that avoids generic AI aesthetics.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 15 edited versions we read keep these.

  • 7

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

    Verify keyboard navigation and focus order.

    line 20
  2. Distinctive:

    Verify semantic markup and labels.

    line 21
  3. Distinctive:

    Verify form errors are announced accessibly.

    line 22
  4. Distinctive:

    Check color contrast and motion sensitivity.

    line 23
  5. Distinctive:

    Check touch target sizing where relevant.

    line 24
  6. Distinctive:

    Do not ship UI changes without labels for interactive controls.

    line 33
  7. Distinctive:

    Do not rely on color alone to convey meaning.

    line 34

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

Use this Skill when

Validating UI, form, or client-rendered changes that users interact with.

Inputs

  • UI diff and screenshots
  • Acceptance criteria
  • Platform expectations (web / iOS)

Procedure

  1. Verify keyboard navigation and focus order.
  2. Verify semantic markup and labels.
  3. Verify form errors are announced accessibly.
  4. Check color contrast and motion sensitivity.
  5. Check touch target sizing where relevant.
  6. Capture accessibility evidence under .agent/evidence/accessibility/.

Output

Accessibility findings with severity, location, and remediation.

Prohibited actions

  • Do not ship UI changes without labels for interactive controls.
  • Do not rely on color alone to convey meaning.

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.