agentleFS
SwitchbackTechSwitchbackTech/compass/.agents/skills/a11y-audit/SKILL.md

a11y-audit

Skill227 starsChanged 50 days agoMITView on GitHub

Audits changed Compass UI for accessibility regressions in semantics, names, keyboard and focus behavior, ARIA, contrast, motion, and testability, then proposes minimal diff-scoped fixes. Use for UI diff reviews, accessibility audits, or flaky interaction tests.

35 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use perf-audit, design-tokens 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.
  • WhatIfWeDigDeeperSkill

    perf-audit

    Profile and optimize React application performance

    Also in 4 projects that use this

  • ilikescienceSkill

    design-tokens

    Expert in design tokens using the DTCG specification. Use this skill when users ask about design tokens, DTCG format, token validation, formatting, transformation, color spaces (sRGB, Display P3, OKLCH), references and aliasing, resolvers, theming with modifiers/contexts, multi-platform design systems, accessibility, or working with tools like jq, jsonata, and terrazzo. Helps with token file creation, resolver configuration, structure, naming conventions, and best practices.

    Also in 4 projects that use this

  • Sagargupta16Skill

    dependency-audit

    Audit project dependencies for security vulnerabilities, licensing issues, maintenance health, and optimization opportunities. Use it during regular security audits (monthly or quarterly); before a major release when you want to ensure the dependency tree is clean; when evaluating whether to adopt or replace a dependency; after a security advisory affects one of your dependencies; when your install times or bundle sizes have grown noticeably.

    Also in 3 projects that use this

  • lbednerSkill

    i18n

    Use when a code or template change introduces a new translation message key, in either the framework CLI (aegis/i18n/locales/) or a generated project's CLI (the app/i18n/locales/ template tree). Covers adding the real English string, stubbing the same key into every other locale for parity, and the separate translation PR that later replaces placeholders with reviewed native text.

    Also in 3 projects that use this

  • GitHubSkill

    refactor

    Surgical code refactoring to improve maintainability without changing behavior. Covers extracting functions, renaming variables, breaking down god functions, improving type safety, eliminating code smells, and applying design patterns. Less drastic than repo-rebuilder; use for gradual improvements.

    Also in 5 projects that use this

  • VercelSkill

    deploy

    Deploy applications to Vercel. Use when the user says "deploy", "deploy to Vercel", "push to production", "deploy my app", or "go live".

    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 28 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. Very specific:

    Do not expand into an unrelated site-wide audit.

    line 30
  2. Distinctive:

    Run the checklist below.

    line 48
  3. Distinctive:

    Every interaction is keyboard reachable and operable.

    line 64
  4. Distinctive:

    Use ARIA only where native semantics are insufficient.

    line 72
  5. Distinctive:

    Test meaningful state and focus outcomes, not only element presence.

    line 89

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

When

UI diff review, accessibility audit, or flaky interaction tests.

Steps

Workflow, then Checklist, scoped to the diff.

Output

Minimal diff-scoped findings and proposed fixes.

Pass

Changed UI reviewed; no site-wide unrelated audit.

Anti-patterns

Do not expand into an unrelated site-wide audit. See anti-patterns.md.

Escalate

A WCAG judgment that needs a human, or a contrast issue that needs design.

Accessibility change audit

Audit the changed UI and its immediate context. Do not turn a diff review into an unrelated site-wide audit.

Workflow

  1. Identify changed elements, interactions, states, and styles.
  2. Exercise affected behavior with the browser tooling available to the current agent when static inspection cannot establish focus, keyboard, contrast, or motion behavior.
  3. Run the checklist below.
  4. Tie each finding to a changed line or behavior and propose the smallest durable fix.
  5. Recommend role/name queries and user-driven tests.

Checklist

Semantics and names

  • Heading order and landmarks remain meaningful.
  • Interactive elements use native buttons, links, inputs, lists, and tables.
  • Inputs, icon controls, dialogs, and regions have accessible names.
  • Helper/error text is connected with aria-describedby when appropriate.

Keyboard and focus

  • Every interaction is keyboard reachable and operable.
  • Focus order follows DOM order; avoid positive tabIndex.
  • Dialogs, menus, and popovers place, contain, and return focus correctly.
  • Composite widgets implement the expected arrow, Home/End, Enter, Space, and Escape behavior.

ARIA and state

  • Use ARIA only where native semantics are insufficient.
  • aria-expanded, aria-selected, aria-pressed, aria-controls, and aria-activedescendant reflect actual state and relationships.
  • Hidden/disabled content is not accidentally focusable.
  • Live updates and errors are announced when users need them.

Visual behavior

  • Text, controls, and focus indicators meet Compass's WCAG 2.2 AA target.
  • Color is not the only state indicator.
  • Motion respects reduced-motion preferences.
  • Zoom, narrow layouts, and reflow do not hide essential controls.

Tests

  • Query by role and accessible name rather than CSS or data-*.
  • Drive interactions with user-event.
  • Test meaningful state and focus outcomes, not only element presence.
  • Reuse existing Playwright/axe checkpoints; add one only for a newly exposed representative state.

Read docs/development/testing-playbook.md#accessibility-testing before changing axe configuration or adding browser checkpoints.

Output

Order findings by blocker, high, medium, then low:

[severity] path:line — problem and user impact
Fix: smallest durable change
Test: semantic assertion or user flow that protects it

State when no findings are confirmed. Separate automation results from judgment-based observations and never claim automated checks establish full WCAG conformance.

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.