Works with the AI tools you already use
Claude Code
Cursor
Codex CLI
Muse
Dots+22 moreClaude CodeCursorCodex CLIMuseDots
OpenClaw
Manus
Grok
Grok Bot+18 agentsWebsite Accessibility Audit Assistant
Audits UI screenshots and code for WCAG 2.2 issues, providing remediation plans and manual testing checklists.
$9.99
Website Accessibility Audit Assistant
Example session with this skill installed
I have a screenshot of a login form with a 'Submit' button, a 'Remember Me' checkbox, and some red text under the password field. Can you audit this for WCAG 2.2 AA?
- Read your context and instructions
- Compiled the website accessibility audit
- Generated the document
I have analyzed the provided login form screenshot for WCAG 2.2 AA alignment. While visual evidence identifies several critical issues, behavioral testing is required for full verification.
Accessibility Audit: Login Form
Findings Summary
| ID | Issue | Status | WCAG | Impact | Priority | Owner |
|---|---|---|---|---|---|---|
| A11Y-001 | Error communication by color only | Observed | 1.4.1 | High | Critical | Designer |
| A11Y-002 | Likely insufficient contrast on 'Remember Me' | Likely | 1.4.3 | Medium | High | Designer |
| A11Y-003 | Ambiguous 'Submit' button accessible name | Verify | 4.1.2 | High | Medium | Developer |
Detailed Findings
Issue: Error communication by color only
Evidence: The error message under the password field is indicated only by red text. There is no icon or text prefix (e.g., "Error:") to assist users with color vision deficiency.
Status: Observed
WCAG Reference: 1.4.1 Use of Color (Level A)
User Impact: Users who cannot perceive color may miss the error state entirely.
Priority: Critical
Remediation: Add a clear text prefix like "Error:" or a unique icon to the message. Ensure the error is programmatically linked to the input via aria-describedby.
Verification: View the page in grayscale to ensure the error remains identifiable.
Manual Testing Checklist
- Keyboard: Can the 'Remember Me' checkbox be toggled using only the Space key?
- Focus: Does the red error message receive focus, or is an
aria-liveregion used to announce it? - [ ]
Screen Reader: Is the 'Submit' button announced as a button, and does the screen reader read the error message when the password field is focused?
- Contrast: Measure the hex code of the red error text against the background; it must meet a 4.5:1 ratio.
Next steps
- Review the color contrast of the 'Remember Me' label using a color picker.
- Implement
aria-invalid="true"on the password field when the error is active. - Add a visible 'Skip to Content' link if this form is part of a larger page layout.
website-accessibility-audit-assistant.pdf
PDF · document
Example file from a real run - the skill writes it into your workspace.
Connects securely to your tools. The creator never sees your data.
What you get
About this skill
The problem
Automated accessibility scanners miss over 60% of WCAG issues, yet manual audits are slow, expensive, and require deep regulatory expertise. Developers and designers often struggle to translate visual UI into concrete compliance requirements or remediation tasks.
What it does
- Analyzes screenshots, Figma exports, and HTML snippets to detect visual and structural accessibility barriers.
- Maps every finding to specific WCAG 2.2 Success Criteria with evidence-based status labels.
- Generates a prioritized remediation roadmap with specific ownership for designers, developers, and content teams.
- Produces a customized manual testing checklist for keyboard navigation, screen readers, and reflow behavior.
- Identifies interactive component risks in modals, menus, and forms that require behavioral verification.
Frameworks & tools
WCAG 2.2, WAI-ARIA, Semantic HTML5, Figma, React, Vue, and standard browser dev tools.
Why this beats prompting it yourself
Standard LLMs often hallucinate ARIA attributes or confidently claim compliance from a single image. This skill enforces a strict evidence-based workflow that distinguishes between observed, likely, and verify-only issues, ensuring you never hand off false positives to a client or team.
Use cases
- Pre-launch accessibility audits for agency-client handoffs.
- Quickly generating a manual QA checklist for a new UI component.
- Converting design mockups into accessibility requirements for development tickets.
- Triaging automated scan results with practical human-centric remediation steps.
Known limitations
Cannot verify screen-reader output or keyboard traps from static images alone. Does not provide legal certification or compliance guarantees.
How to install
Works the same in every agent - Claude, Cursor, Codex, Copilot and 20+ more.
- 1
Download the ZIP
Free skills download straight away. Paid skills unlock right after purchase.
- 2
Unzip into your skills folder
Every agent reads skills from one folder on your machine. Drop the unzipped folder in there.
- 3
Ask your agent to use it
Restart the agent if it was already running. It picks the skill up automatically - no config needed.
Skills folder by agent
Click the path to copy it. Create the folder if it does not exist yet.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill passes our trust checks below.
Security scanned
Passed our 8-point scan before listing
Fresh listing
Recently published to Agensi
30-day refund
Not a fit? Get your money back
Trust & safety
Security scanned
Verified clean 10 days ago
- Passed all security checks, Safe to install