agentsclimarketplace

Frontend a11y

Skill tmj-90/gaffer/runner/skills/frontend-a11y

Self-hosted AI coding factory — sandboxed agents deliver tickets to merged code, gated by a human in a dashboard. Local-first, cost-transparent, human-in-the-loop.

Install
npx -y skills add tmj-90/gaffer --skill frontend-a11y

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when a ticket requires accessibility work or when delivering UI that must be usable by everyone — keyboard navigation, screen-reader labelling, focus management, colour contrast, or reduced-motion support. Invoke for "make X accessible", "fix the a11y issues", "add keyboard support", or as a companion check on any new component.

SKILL.md

2.4 KB, as published. Nobody here has run it

Make the UI accessible

Bring the affected UI to WCAG 2.2 AA: operable by keyboard, understandable to assistive tech, and tolerant of user preferences — proven, not assumed.

Steps

  1. Read the lore first. Call search_lore (Memory MCP) for the repo's accessibility conventions and any design-system a11y primitives already in use.
  2. Use semantic HTML before ARIA. Reach for the native element (button, a, label, nav, dialog) first; add ARIA roles/attributes only to fill real gaps.
  3. Make it keyboard operable. Every interactive element must be focusable and activatable by keyboard, in a logical tab order, with a visible focus indicator.
  4. Label everything. Associate inputs with labels, give icon-only controls an accessible name, and announce dynamic changes with live regions where needed.
  5. Manage focus for overlays/dialogs/menus: move focus in on open, trap it while open, restore it on close.
  6. Respect preferences. Honour prefers-reduced-motion; ensure text/background contrast meets AA (4.5:1 body, 3:1 large text).
  7. Verify + evidence. Run the repo's automated a11y checks and exercise keyboard flow; record the results via the record-evidence skill and submit for review.

Rules

  • Native semantics over ARIA; never use ARIA to paper over the wrong element.
  • No keyboard trap, no focus loss, no invisible focus.
  • Don't remove focus outlines without a compliant replacement.
  • Colour is never the only signal — pair it with text or icon.

Capture lore

This skill is one of the places durable, reusable knowledge naturally surfaces: An accessibility pattern or boundary this repo standardises on — a focus-management rule, a semantics convention, or an a11y check that must pass. That kind of fact is lore. Capture it via the lore-capture protocol in your brief (CLAUDE.factory.md, step 11 "Memory contribution"): call the Memory MCP suggest_lore once at the close of your work — reusable conventions, gotchas, decisions, and boundaries only, never per-ticket trivia.

Gives 1 of the 12 instructions most accessibility skills give

Counted across 384 of the 385 authors here whose files we hold, read 2026-08-06

  • maintain visible focus indicatorsin 46 of 384, across 33 files
  • run automated accessibility scansin 44 of 384, across 32 files
  • make all interactive elements keyboard reachablein 39 of 384, across 32 files
  • use semantic HTML before ARIAhere, and in 38 of 384
  • respect reduced motion preferencesin 35 of 384, across 27 files
  • Associate labels programmatically with inputsin 33 of 384, across 26 files
  • Use native elements over ARIAin 30 of 384, across 18 files
  • test with a screen readerin 26 of 384, across 22 files
  • map findings to WCAG criteriain 24 of 384, across 14 files
  • meet minimum color contrast ratiosin 24 of 384, across 16 files
  • Provide text alternatives for imagesin 24 of 384, across 18 files
  • trap focus inside open modalsin 23 of 384, across 18 files

Said here and by no other author read

  • search lore for accessibility conventions
  • label all inputs and icon-only controls
  • manage focus for overlays dialogs and menus
  • run automated a11y checks and exercise keyboard flow
  • record results and submit for review
  • suggest reusable accessibility lore

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.