skills.rest
yonetim258852
yonetim258852COMMUNITY
Explore all skills by this author →
GitHub

accesslint-audit

Audit live URLs or HTML files for WCAG 2.2 accessibility issues.

Updated May 24, 2026
Search Tags:#automation#accessibility#a11y#audit#wcag#web-development#live-dom
One-click install
npx skills add https://github.com/yonetim258852/ozgur-os --skill accesslint-audit
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accesslint-audit
Source: https://github.com/yonetim258852/ozgur-os/tree/main/.claude/skills/accesslint-audit
Command: npx skills add https://github.com/yonetim258852/ozgur-os --skill accesslint-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Accessibility auditing of codebases and web pages to identify WCAG 2.2 violations and guide remediation.

Core Features & Use Cases

  • Live-DOM auditing for URLs using audit_live to catch issues in the rendered page.
  • Static HTML/file auditing with audit_html for non-URL targets and for pre-rendered content.
  • Supports two workflows: report (scan-only) and fix (audit→edit→verify loop) with actionable guidance.

Quick Start

Audit a target URL or HTML snippet for accessibility issues and generate a prioritized report.

Frequently Asked Questions about accesslint-audit

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

FAQPage Schema
How do I audit a live web page for WCAG compliance issues?▼

You can audit a live URL for WCAG compliance issues by using the audit_live function, which scans the rendered page in a headless Chrome environment. It returns structured results containing WCAG rule IDs and actionable guidance.

Can I check raw HTML files for accessibility issues without a live URL?▼

Yes, you can check raw HTML files for accessibility issues without a live URL by using the audit_html function. This scans static HTML snippets and pre-rendered content to identify WCAG 2.2 violations.

Do I need a headless Chrome environment to run accessibility audits?▼

Yes, a headless Chrome environment is required to run live accessibility audits on URLs. The audit_live function relies on headless Chrome to render the target web page and evaluate the live DOM for WCAG violations.

What is the difference between the report and fix workflows for accessibility auditing?▼

The report workflow is a scan-only mode that generates a prioritized list of accessibility issues. The fix workflow performs an audit, applies code edits, and verifies the changes to guide remediation and ensure WCAG compliance.

How do I wait for dynamic content to load before auditing a URL?▼

You can wait for dynamic content to load before auditing a URL by using the optional wait_for and selector parameters in the audit_live function. This ensures the headless Chrome environment fully renders the target elements before scanning for WCAG issues.

Related Skills

Explore More Software Engineering Skills→
Zenobia000Zenobia000
20

community-a11y-audit

Detect and fix WCAG 2.2 accessibility issues in web content.

Community
Intermediate
ProjectEuropaProjectEuropa
4

wcag-audit-patterns

Identify WCAG 2.2 conformance issues and provide remediation guidance across web content.

Community
Advanced
abhishekdutta18abhishekdutta18

browser-qa

Automate visual, functional, and accessibility testing of web pages.

Community
Intermediate
dominika-zajacdominika-zajac

accessibility-audit

Run Lighthouse audits and custom heuristics to report WCAG accessibility issues.

Community
Advanced