agentleFS
EstebanT1112EstebanT1112/codex-engineering-workflow/skills/fixing-accessibility/SKILL.md

fixing-accessibility

Skill0 starsChanged 2 months agoMITView on GitHub

Audit and fix accessibility problems in web interfaces, including semantics, names, keyboard access, focus, forms, dialogs, status messages, contrast, zoom, and motion preferences. Use for explicit accessibility work or when implementing interactive web controls with material accessibility risk.

19 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use fixing-motion-performance, ui-skills-root and 9 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.
  • kapishdimaSkill

    fixing-motion-performance

    Fix animation performance issues.

    Also in 7 projects that use this

  • Discriminative-shoji607Skill

    ui-skills-root

    Use before UI-related work to select the smallest useful UI Skills context through the ui-skills CLI.

    Also in 3 projects that use this

  • Discriminative-shoji607Skill

    improve-ui

    Audit an existing product surface against its own design evidence, identify verified UI problems, and write self-contained implementation plans for another agent. Strictly read-only on product source. Use when asked to review, refine, improve, or clean up an interface without replacing its identity; investigate design-system drift; or prepare a design handoff.

    Also in 3 projects that use this

  • studio-lgtmSkill

    make-interfaces-feel-better

    Apply design engineering best practices to polish UI components - use when reviewing or improving interfaces, animations, typography, or interaction details.

    Also in 4 projects that use this

  • swyxioSkill

    mobile-native

    Apply swyx's native mobile UX preferences when designing or critiquing iPhone/iPad flows, adapting tablet layouts, choosing communication-app notification behavior, or opening notifications/deep links/widgets/shortcuts before local content is ready. Also use for iOS/iPadOS generated build configuration, signing/install/launch problems, and device playtesting. Keep existing native or cross-platform stacks; excludes browser-only responsive work and backend-only changes without native UX or delivery implications.

    Also in 3 projects that use this

  • wxyhgkSkill

    improve-animations

    Survey a codebase's animation and motion code as a senior motion advisor, then produce a prioritized audit and self-contained implementation plans for other agents (or cheaper models) to execute. Read-only on source code — it plans improvements, it does not apply them. Use when the user asks to "improve the animations", "audit the motion", "make this app feel better", or wants a roadmap of animation fixes rather than a review of a single diff.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 18 edited versions we read keep these.

  • 4

    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:

    Prefer native HTML semantics.

    line 15
  2. Distinctive:

    Add a focused automated assertion when it can prevent regression.

    line 18
  3. Distinctive:

    Verify with repository checks and a bounded manual keyboard review.

    line 19
  4. Distinctive:

    Do not claim WCAG conformance from lint or component tests alone.

    line 23
  5. Very specific:

    Do not add redundant roles, positive tabindex, or broad ARIA workarounds.

    line 24
  6. Very specific:

    Use the separate native accessibility capability when it is installed and the target is React Native, iOS, or Android.

    line 25

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

Fixing Web Accessibility

Workflow

  1. Identify the affected user journey and the repository's existing accessibility tools.
  2. Reproduce the problem with semantic inspection and keyboard use before changing code.
  3. Prefer native HTML semantics; add ARIA only when native elements cannot express the interaction.
  4. Repair accessible names, relationships, focus order, visible focus, error association, live feedback, contrast, zoom/reflow, and reduced motion as applicable.
  5. Preserve behavior for pointer and touch users while adding keyboard and assistive-technology support.
  6. Add a focused automated assertion when it can prevent regression.
  7. Verify with repository checks and a bounded manual keyboard review. Report screen-reader or browser testing as skipped when it was not actually performed.

Boundaries

  • Do not claim WCAG conformance from lint or component tests alone.
  • Do not add redundant roles, positive tabindex, or broad ARIA workarounds.
  • Use the separate native accessibility capability when it is installed and the target is React Native, iOS, or Android.

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.

Reviews can't be read right now.

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.