
AccessLint Scan
FreeAudit live pages for accessibility issues with precision.
Free · Opens the source repo
What AccessLint Scan does
AccessLint Scan is a command-line tool designed to help developers and designers audit live web pages for accessibility issues based on WCAG standards. It provides a detailed report that identifies violations, including their locations on the page, without attempting to fix them. This means you can focus on understanding the accessibility barriers present in your application without the risk of unintended changes to the codebase. The skill is particularly useful for teams looking to ensure their web applications are accessible to all users, including those with disabilities.
To use AccessLint Scan, you simply need to run a command that specifies the URL of the page you want to audit. The tool will launch a Chrome instance to analyze the page and return a JSON report that includes counts of violations categorized by impact, along with specific details about each issue. Each entry in the report provides the exact location of the violation using CSS selectors, evidence of the issue such as contrast ratios or missing attributes, and a suggested fix, which may require human intervention for more complex issues.
This skill is ideal for web developers, accessibility specialists, and quality assurance teams who need to perform regular audits as part of their development workflow. By integrating AccessLint Scan into your process, you can proactively identify and address accessibility issues before they reach production, improving the overall user experience for individuals with disabilities. The tool is straightforward to use, making it accessible even to those who may not have extensive experience with accessibility audits.
However, it is important to note that AccessLint Scan should not be used as a substitute for comprehensive accessibility testing or expert review. It provides a starting point for identifying issues, but further validation and testing may be necessary to ensure compliance with accessibility standards in specific environments.
When to use it
Use this skill when you need to audit a live web page for accessibility issues and require a detailed report of violations without making any edits.
When not to use it
This tool is not suitable for fixing accessibility issues directly or for environments where manual review and testing are required to ensure compliance.
What you can build with it
Regular Accessibility Audits
Incorporate AccessLint Scan into your development workflow to perform regular audits of your web applications.
Identifying WCAG Violations
Use the tool to pinpoint specific WCAG violations on live pages, ensuring compliance and improving user experience.
Quality Assurance Checks
Leverage AccessLint Scan during QA processes to catch accessibility issues before deployment.
How to install AccessLint Scan
View source1. Install with the skills CLI
npx skills add sickn33/agentic-awesome-skills/accesslint-scan --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by sickn33Audit a live page and report what's broken and where. Locate; don't fix. If no URL in $ARGUMENTS, ask for one.
When to Use
- 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.
1. Audit
PORT=$(npx -y @accesslint/chrome@latest ensure | node -e 'process.stdin.on("data",d=>process.stdout.write(""+JSON.parse(d).port))')
npx -y @accesslint/cli@latest "<url>" --port "$PORT" --format json
Flags as needed: --selector, --wait-for "<selector>", --include-aaa, --disable <rules>.
2. Report
Counts by impact, then one entry per violation:
- where — selector verbatim +
file:line (symbol)ifsourceis present — never fabricate. If no violation hassource, note "source mapping unavailable — located by selector only". - evidence — contrast ratio, missing attribute, empty name
- fix — mechanical change or
NEEDS HUMAN
Don't edit. For fixes: apply mechanical ones then re-run to verify; for bulk work hand off to accesslint:audit.
3. Tear down
npx -y @accesslint/chrome@latest stop --all # skip if ensure reported "managed":false
Gotchas
ensurealways determines the port — never hardcode 9222.- CLI exit 2 = bad URL or page never loaded; check the dev server.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
Frequently asked questions about AccessLint Scan
Similar skills
Playwright Component Testing
Test React and Vue components in isolation with Playwright.
Fluent UI Blazor
Integrate Fluent UI components in Blazor applications effortlessly.
Build MCP App
Create interactive UI widgets for MCP servers.
Web Design Reviewer
Identify and fix design issues in websites efficiently.
Markstream Install
Seamlessly integrate Markstream for Markdown rendering.
GSAP & Framer Scroll Animation
Create advanced scroll animations effortlessly.
