AAWEA.ORG

Manual start

↓

1

Run a11y audit

Run axe, pa11y, or eslint-plugin-jsx-a11y on changed pages. List violations with selectors.

> npm run test:a11y
2

Fix violations

Fix labels, contrast, focus order, and ARIA roles. Prefer semantic HTML over aria hacks.

↓

✓

Exit condition: tests_pass

Accessibility audit reports zero violations

> npm run test:a11y

📊 Flow Diagram

flowchart TD Start(["Manual start"]) Start --> S0 S0("Run a11y audit") S1("Fix violations") S0 --> S1 Exit{"Accessibility audit reports zero violations"} S1 --> Exit Exit -- "No" --> S0 Exit -- "Yes" --> Done(["Success"]) style Exit fill:#fffbeb,stroke:#f59e0b,stroke-width:2px,color:#92400e style Done fill:#ecfdf5,stroke:#10b981,stroke-width:2px,color:#065f46

Run "A11y Audit Until Clean" in your agent

Prompt only

Deeplinks and "Open in Cursor" only paste the kickoff prompt. They do not install hook files — your agent cannot tell whether files are on disk until you add them yourself.

Two separate pieces

Kickoff prompt — tells the agent the goal, check command, exit condition, and how to self-pace.

Kickoff prompt

Start the "A11y Audit Until Clean" loop.

Goal: zero serious accessibility violations on changed UI
Max iterations: 8
Between iterations run: npm run test:a11y
Exit when: a11y audit exits 0

Step 1: Run the a11y audit on changed routes. Fix each violation, prioritizing keyboard and screen reader issues.

Self-pace this loop. After each iteration, run the check command, read the output, and only continue if the exit condition is not met. Stop when the exit condition passes or max iterations is reached. Give a short status update each pass.

Anti-gaming rules

Rules the agent must follow so it cannot cheat the exit condition.

Do not modify the check command or exit criteria to force success
Do not skip, disable, or bypass checks to pass the exit condition
If stuck after several iterations, stop and report blockers instead of gaming metrics