About this Skill
Locate mechanically detectable accessibility issues on one rendered page, with DOM selectors, evidence and source locations when available.
Why we picked it
Scan a live page and produce a worklist without editing source.
What it helps with
- Scan a live page and produce a worklist without editing source.
- Retain evidence and distinguish automated findings from checks needing a person.
Workflow and expected result
Step 1
Resolve the target URL, scope and relevant baseline or assessment inputs.
Step 2
Scan a live page and produce a worklist without editing source.
Step 3
Record findings, verification limits and the next action for each unresolved issue.
Source review
Reviewed the task instructions and repository inventory at commit 2e9d73366783. This listing describes the upstream workflow; it does not claim that a full product implementation or accessibility audit was executed during intake.
Reviewed upstream task instructionsOfficial repository and installation guide
Before you use it
- A coding assistant with local file access and Node.js for the upstream installer. Review the installed instructions before use.
- Node.js, network access and Chrome are needed by @accesslint/cli and @accesslint/chrome. The page must be running; source mapping depends on available framework metadata.
- A successful automated check does not certify full accessibility conformance.
Supported agents
Sources & references
Original sources are linked below. Practical starting points are editorial suggestions from SkillHey.
