accesslint-scan

Audits live pages for WCAG violations with precise DOM selectors and source references.

Updated May 24, 2026
One-click install
npx skills add https://github.com/yonetim258852/ozgur-os --skill accesslint-scan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: accesslint-scan
Source: https://github.com/yonetim258852/ozgur-os/tree/main/.claude/skills/accesslint-scan
Command: npx skills add https://github.com/yonetim258852/ozgur-os --skill accesslint-scan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit live pages for accessibility issues and report each violation with precise DOM selectors and source references. This enables developers and testers to pinpoint exactly where WCAG violations occur and prioritize fixes without manual page inspection.

Core Features & Use Cases

  • Audit live pages for WCAG violations with precise DOM selectors and source references.
  • Targeting by URL or by config targets (e.g., accesslint.config.json), with a default target fallback.
  • Non-destructive reporting: outputs a debuggable worklist to guide fixes without editing the page.

Quick Start

Run an accessibility audit against a URL or config target and review the resulting WCAG violations.

Frequently Asked Questions about accesslint-scan

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a live web page for WCAG violations?

You can audit a live web page for WCAG violations by passing a URL to the scanner, which launches a debuggable Chrome instance and outputs a worklist of issues with precise DOM selectors and source references.

What is the best way to find DOM selectors for accessibility issues?

Finding precise DOM selectors for accessibility issues is handled by running an audit against your live page, which reports each violation with exact selectors and source locations to guide code fixes.

Can I scan multiple environments using an accessibility config target?

Yes, you can scan multiple environments by defining targets in an accesslint.config.json file and passing the target name, or omitting arguments to audit the default target automatically.

Does the accessibility audit modify the page during testing?

No, the accessibility audit is non-destructive and does not modify the page; it outputs a debuggable worklist of WCAG violations to guide your fixes without altering the live DOM.

How does a CDP-based Chrome engine detect web accessibility issues?

A CDP-based Chrome engine detects web accessibility issues by running an audit in a debuggable browser instance, inspecting the live DOM to pinpoint WCAG violations and report exact source references.