About this Skill
Compare a rendered page with a change baseline and report newly introduced, resolved and pre-existing accessibility issues.
Why we picked it
Check a UI change for accessibility regressions using a branch or working-tree baseline.
What it helps with
- Check a UI change for accessibility regressions using a branch or working-tree baseline.
- 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
Check a UI change for accessibility regressions using a branch or working-tree baseline.
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 Git, Node.js, Chrome and a running rebuildable site. The documented default uses stash and restore; branch mode switches checkouts, so review the workflow before running it.
- 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.
