Accesslint
Find and fix WCAG 2.2 accessibility problems with codebase sweeps and audit→fix→verify loops from your coding agent.
Overview
accesslint is a plugin marketplace for the Ship phase that exposes WCAG 2.2 audit, fix, and verify loops—including live-DOM Chrome audits—for coding agents.
What is this marketplace?
- WCAG 2.2 focused find-and-fix workflows via the audit skill
- Codebase sweeps plus audit→fix→verify iteration loops
- Live-DOM audits auto-launch Chrome through @accesslint/chrome
- Single accesslint plugin (v0.8.0) in the AccessLint marketplace
- No manual Chrome setup required for live-DOM audit paths
- Marketplace bundles 1 plugin (accesslint v0.8.0)
Community signal: 54 GitHub stars.
What problem does it solve?
Shipping accessible UI is slow when WCAG issues are found late and agents lack a repeatable audit→fix→verify loop with a real browser DOM.
Who is it for?
Builders preparing SaaS or marketing sites for accessibility compliance who want agent-guided WCAG 2.2 workflows in Claude Code or similar agents.
Skip if: Native mobile-only apps with no web surface, or teams that only need a one-off Lighthouse score without fix loops.
What do I get? / Deliverables
After you add the marketplace, your agent can sweep code and live pages for WCAG 2.2 issues, apply fixes, and re-verify without manual Chrome setup.
- WCAG 2.2 issue reports from codebase or live-DOM audits
- Agent-guided fix iterations with re-verification passes
- Launch-readier accessible UI evidence after audit loops complete
Plugins in this marketplace
1 plugin — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
Ship/review is the canonical shelf because the plugin centers on compliance auditing and verification before release, not initial UI design. review matches audit skills, sweep passes, and fix-verify loops that gate shipping accessible interfaces.
How it compares
Accessibility audit-and-fix plugin marketplace, not a generic SEO or performance-only ship checklist.
Common Questions / FAQ
Who is Accesslint for?
Solo builders and small front-end teams who ship web products and need WCAG 2.2 coverage with agent-assisted remediation.
When should I use Accesslint?
Use it during Ship review or late Build frontend passes before launch, and whenever you need live-DOM verification after UI changes.
How do I add Accesslint to my agent?
Add the AccessLint/skills marketplace, install the Accesslint plugin from ./plugins/Accesslint, then invoke the audit skill; live-DOM runs use @Accesslint/chrome automatically.