agentleFS
Sign inStart free
malinskibeniaminmalinskibeniamin/skills/accessibility/SKILL.md

accessibility

Skill4 starsChanged 10 days agoMITView on GitHub

Use when React needs ARIA, keyboard, focus, form, or nested-control accessibility.

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

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

  • 0

    Common

    Most of the 112 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 7

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    The local hook: only pairs tablist with child tab roles and data-invalid with aria-invalid.

    line 17
  2. Very specific:

    Do not duplicate checks. Escape hatch: // allow: a11y-skip [reason].

    line 20
  3. Very specific:

    Prefer native controls and visible text.

    line 24
  4. Distinctive:

    Keep clickable containers free of interactive descendants.

    line 26
  5. Very specific:

    Use aria-label only without a visible name.

    line 29
  6. Distinctive:

    Keep a contrasting 2px focus indicator.

    line 38
  7. Very specific:

    Avoid color-only state; pair color with text, icon, or shape and support forced colors with currentcolor.

    line 42
  8. Very specific:

    Keep touch targets at least 44 by 44 CSS pixels.

    line 44
  9. Very specific:

    Verify high-risk mobile overlays on a physical device or simulator, including visualViewport, safe areas, focus, and inertness.

    line 48

“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

Manual WCAG checks: load better-accessibility.

One owner per rule:

  • Biome owns image alt, custom-control keyboard support, combobox ARIA and labels.
  • React Doctor owns structure and naming: dialogs, nested controls, accessible names, persistent labels, and described invalid fields.
  • The local hook only pairs tablist with child tab roles and data-invalid with aria-invalid.

Do not duplicate checks. Escape hatch: // allow: a11y-skip [reason].

Interaction contracts

  • Prefer native controls and visible text. Custom clickable elements need a role, tabIndex, and equivalent keyboard behavior.
  • Keep clickable containers free of interactive descendants; otherwise use a passive container. Never nest pressables.
  • Comboboxes expose aria-expanded and aria-controls; tablists contain tabs.
  • Use aria-label only without a visible name; it or aria-labelledby can replace descendant text. Omit redundant words such as icon or button.
  • Form controls have persistent labels. Connect visible errors with aria-invalid and a current aria-describedby; remove stale error IDs when validation clears.
  • Unclear names: inspect the accessibility tree; follow WAI-ARIA naming guidance.

Visual and focus checks

  • Keep a contrasting 2px focus indicator; expose hover actions to keyboard and touch users.
  • DOM order matches reading and tab order. Reordered layouts need keyboard and screen-reader evidence.
  • Modal surfaces trap and restore focus and make the background inert.
  • Avoid color-only state; pair color with text, icon, or shape and support forced colors with currentcolor.
  • Keep touch targets at least 44 by 44 CSS pixels. Gate hover-only effects with @media (hover: hover) and (pointer: fine).
  • For reduced motion, preserve feedback through opacity, color, text, or instant state changes.
  • Support 200% text zoom without loss.
  • Verify high-risk mobile overlays on a physical device or simulator, including visualViewport, safe areas, focus, and inertness.

Setup (install, AXE, hooks): SETUP.md.

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