About this Skill
Inspect keyboard behavior, focus, widget states, reflow and other checks that an automated accessibility scanner cannot settle.
Why we picked it
Exercise a live page and separate verified evidence from human review and untested criteria.
What it helps with
- Exercise a live page and separate verified evidence from human review and untested criteria.
- 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
Exercise a live page and separate verified evidence from human review and untested criteria.
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.
- Needs a running page and a browser MCP such as Chrome DevTools, Playwright or Puppeteer. Without one, only static checks and explicit human handoffs are available.
- 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.
