agentleFS
ankitluthraankitluthra/frontend-quality-graph/skills/frontend-a11y/SKILL.md

frontend-a11y

Skill0 starsChanged 3 months agoMITView on GitHub

Reviews frontend UI for accessibility — semantics, keyboard, focus, labels, contrast, and forms. Invoked automatically by frontend-graph; enrich with web-design-guidelines when that skill is installed.

11 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 1

    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. Very specific:

    If web-design-guidelines is installed, apply its accessibility / focus / forms rules in addition to the checklist below.

    line 13
  2. Distinctive:

    No keyboard traps; dialogs dismissible accessibly

    line 24

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

Frontend a11y review

Return PASS or FAIL. Focus on changed UI.

If web-design-guidelines is installed, apply its accessibility / focus / forms rules in addition to the checklist below.

Must-check

  1. Interactive elements keyboard-reachable; focus order sane
  2. Real controls (not clickable divs) unless unavoidable
  3. Meaningful images have alt; decorative images hidden
  4. Form inputs labeled; errors associated
  5. Plausible contrast for text/icons on used backgrounds
  6. Focus visible on interactive elements
  7. Heading hierarchy / landmarks where appropriate
  8. No keyboard traps; dialogs dismissible accessibly

Output format

VERDICT: PASS|FAIL
Findings:
- [file or area] issue → fix
(max 8)

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.