accesslint-scan
starsforks
How to install accesslint-scan?
sickn33/agentic-awesome-skills/accesslint-scan
$npx -y skills add sickn33/agentic-awesome-skills --skill accesslint-scanAudit a live page for accessibility issues, locate each WCAG violation precisely, and return a selector-grounded fix worklist without editing.
SKILL.md
| 1 | Audit a live page and report what's broken and where. Locate; don't fix. If no URL in `$ARGUMENTS`, ask for one. |
| 2 | |
| 3 | ## When to Use |
| 4 | - Use this skill when the task matches this description: Audit a live page for accessibility issues, locate each WCAG violation precisely, and return a selector-grounded fix worklist without editing. |
| 5 | |
| 6 | ## 1. Audit |
| 7 | |
| 8 | ```bash |
| 9 | PORT=$(npx -y @accesslint/chrome@latest ensure | node -e 'process.stdin.on("data",d=>process.stdout.write(""+JSON.parse(d).port))') |
| 10 | npx -y @accesslint/cli@latest "<url>" --port "$PORT" --format json |
| 11 | ``` |
| 12 | |
| 13 | Flags as needed: `--selector`, `--wait-for "<selector>"`, `--include-aaa`, `--disable <rules>`. |
| 14 | |
| 15 | ## 2. Report |
| 16 | |
| 17 | Counts by impact, then one entry per violation: |
| 18 | |
| 19 | - **where** — selector verbatim + `file:line (symbol)` if `source` is present — never fabricate. If no violation has `source`, note "source mapping unavailable — located by selector only". |
| 20 | - **evidence** — contrast ratio, missing attribute, empty name |
| 21 | - **fix** — mechanical change or `NEEDS HUMAN` |
| 22 | |
| 23 | Don't edit. For fixes: apply mechanical ones then re-run to verify; for bulk work hand off to `accesslint:audit`. |
| 24 | |
| 25 | ## 3. Tear down |
| 26 | |
| 27 | ```bash |
| 28 | npx -y @accesslint/chrome@latest stop --all # skip if ensure reported "managed":false |
| 29 | ``` |
| 30 | |
| 31 | ## Gotchas |
| 32 | |
| 33 | - `ensure` always determines the port — never hardcode 9222. |
| 34 | - CLI exit 2 = bad URL or page never loaded; check the dev server. |
| 35 | |
| 36 | ## Limitations |
| 37 | - Use this skill only when the task clearly matches the scope described above. |
| 38 | - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. |
| 39 | - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing. |
People who liked this also viewed
6 picksType
- tddSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- test-driven-developmentUse when implementing any feature or bugfix, before writing implementation codeSkillsJul 2026
- qaSkills for Real Engineers. Straight from my .agents directory.SkillsJul 2026
- verification-before-completionUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidenceSkillsJul 2026
- webapp-testingToolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser lSkillsJul 2026
- playwright-best-practicesUse when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling authentication or OAuth, teSkillsJul 2026
