agentleFS
UwayxtUwayxt/agent-skills/.agents/skills/accessibility-review/SKILL.md

accessibility-review

Skill4 starsChanged 3 months agoMITView on GitHub

Audit against WCAG 2.1 AA across perceivable, operable, understandable, robust. Use when accessibility, a11y, WCAG, contrast, screen reader, tap target, or is this accessible.

19 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

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

  • 0

    Common

    Most of the 16 edited versions we read keep these.

  • 4

    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:

    Non-text content: Every image, icon, and chart has alt text or aria-label.

    line 12
  2. Distinctive:

    Keyboard navigation: Every interactive element is reachable via Tab and activatable via Enter/Space.

    line 16
  3. Distinctive:

    Labels: Every form input has a visible label (not just placeholder text).

    line 22
  4. Very specific:

    Semantic HTML: Use <button> for actions, <a> for navigation, <nav>, <main>, <header>, <footer> for landmarks.

    line 28
  5. Distinctive:

    ARIA: Use ARIA roles/properties only when semantic HTML is insufficient.

    line 29

“Common” is measured: kept by at least 6 in 10 of the 16 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 is a Constraint, Not a Checkbox

Accessibility is not a checkbox at the end — it's a constraint from the start. Every inaccessible element is a user you've locked out. Audit against WCAG 2.1 AA as the baseline; anything less is a known risk.

1. Perceivable

  • Color contrast: Text against background meets 4.5:1 for normal text, 3:1 for large text. Check every color pairing in the design tokens.
  • Non-text content: Every image, icon, and chart has alt text or aria-label.
  • State indicators: Color is not the sole indicator of state (error = red + icon + text, not just red).

2. Operable

  • Keyboard navigation: Every interactive element is reachable via Tab and activatable via Enter/Space. Tab order follows visual order.
  • Focus indicators: Visible focus ring on every focusable element. Never outline: none without a replacement.
  • Tap targets: Minimum 44×44px on touch devices.
  • No keyboard traps: Modals, dropdowns, and popovers must allow escape via Esc.

3. Understandable

  • Labels: Every form input has a visible label (not just placeholder text).
  • Error messages: Specific ("Email must contain @"), not generic ("Invalid input").
  • Language: Page declares lang attribute.
  • Predictable: Similar things behave similarly across the product.

4. Robust

  • Semantic HTML: Use <button> for actions, <a> for navigation, <nav>, <main>, <header>, <footer> for landmarks.
  • ARIA: Use ARIA roles/properties only when semantic HTML is insufficient.
  • Heading hierarchy: h1 → h2 → h3, no skipping levels.

Output Format

  • Accessibility audit checklist: criterion → pass/fail → evidence → fix recommendation.
  • Summary: total pass, total fail, severity of failures.

Completion Criteria

Done when every criterion in the 4 categories has been evaluated. Not done if "we'll check accessibility later."

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.