agentleFS
Sign inStart free
charanjit-singhcharanjit-singh/lovable-skills/skills/accessibility-pass/SKILL.md

accessibility-pass

Skill10 starsChanged 6 months agoMITView on GitHub

Use when reviewing or fixing accessibility: keyboard navigation, focus order, labels, color contrast, screen reader support, or ARIA attributes. Not for SEO-only or performance-only audits.

3 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

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    All interactive elements reachable by Tab.

    line 15
  2. Very specific:

    Every input has <Label htmlFor> or aria-label.

    line 21
  3. Very specific:

    Use <button> for actions, <a href> for navigation.

    line 24
  4. Distinctive:

    Do not rely on color alone for state (add icon/text).

    line 34

“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

Accessibility pass

Report findings as: critical (blocks users), serious, minor.

Keyboard and focus

  • All interactive elements reachable by Tab; visible focus ring.
  • Modals trap focus; Escape closes.
  • No tabIndex={0} on non-interactive divs for click hacks — use <button>.

Labels and semantics

  • Every input has <Label htmlFor> or aria-label.
  • Icon-only buttons have aria-label.
  • Images: alt descriptive or alt="" if decorative.
  • Use <button> for actions, <a href> for navigation.

Forms

  • Errors linked with aria-describedby / FormMessage.
  • Required fields indicated in label or aria-required.

Color and motion

  • Text contrast ≥ 4.5:1 (normal), 3:1 large text.
  • Do not rely on color alone for state (add icon/text).
  • Respect prefers-reduced-motion for large animations.

Tables and dynamic content

  • <th scope="col"> on data tables.
  • aria-live="polite" for toast/alert regions when appropriate.

Avoid

  • div onClick without role/keyboard support.
  • Auto-playing media with sound.
  • Removing focus outlines without replacement.

Deliverable

Checklist table: issue | location | fix | severity.

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