- Home
- Skills
- Testing & Debugging
- Website Accessibility Audit Agent
Works with the AI Agents you already use
Website Accessibility Audit Agent
Audit web code and UI screenshots for WCAG barriers with prioritized remediation plans and code fixes.
$9.99
Website Accessibility Audit Agent
Example session with this skill installed
- Read your context and instructions
- Compiled the website accessibility audit
I have reviewed the login form snippet and the reported focus visibility issue. The review targets WCAG 2.2 AA standards based on the provided HTML and visual evidence.
Executive Summary
The primary barriers involve missing semantics for interactive elements and lack of visual focus indicators, which prevent keyboard-only users from completing the login flow.
Prioritized Findings
| ID | Issue | Location | Severity | Confidence | Impact | WCAG |
|---|---|---|---|---|---|---|
| A01 | Non-semantic button | .btn div | Critical | Confirmed | Keyboard/Screen Reader block | 2.1.1, 4.1.2 |
| A02 | Missing Alt Text | img tag | Medium | Confirmed | Context loss for SR users | 1.1.1 |
| A03 | No Focus Indicator | Global/Form | High | Confirmed | Visual tracking failure | 2.4.7 |
Detailed Remediation Notes
A01: Non-semantic button
- Severity / Confidence: Critical / Confirmed
- Evidence observed:
<div>withonclickbut no role or tab indexing. - User impact: Keyboard users cannot tab to the element; screen readers identify it as plain text.
Recommended fix: Replace the div with a native button element to inherit focusability and "button" role automatically.
- Example:
<button type="submit" class="btn">Submit</button>
Retest steps: Tab through the form to ensure the button receives focus. Press "Enter" to trigger the login function.
A03: Missing Focus Indicator
- Severity / Confidence: High / Confirmed (from screenshot)
- Evidence observed: Screenshot shows no visual change when form elements are active.
- User impact: Sighted keyboard users cannot determine which element currently has input focus.
Recommended fix: Ensure CSS does not use outline: none without a visible alternative. Use :focus-visible for modern browsers.
- Example:
.btn:focus-visible { outline: 3px solid blue; outline-offset: 2px; }
Retest steps: Navigate the form using the Tab key and verify a high-contrast border appears around every interactive element.
Next steps
- Replace
divandspantriggers with native<button>or<a>tags. - Add descriptive
altattributes to all informative images. - Remove CSS rules that suppress default browser focus outlines.
Connects securely to your tools. The creator never sees your data.
About this skill
Accessibility audits shouldn't rely on guesswork or generic checklists that ignore your actual code. This skill analyzes HTML snippets, screenshots, and scan logs to identify specific WCAG barriers and provide developer-ready remediation steps. It bridges the gap between raw automated data and actionable PRs by mapping evidence to user impact.
What it does
- Evidence-based auditing analyzes provided HTML, screenshots, and manual test notes to find accessibility gaps.
- Prioritized triage assigns severity based on user impact and task blocking, ranging from Low to Critical.
- Remediation mapping provides specific code fixes for identified issues, prioritizing native HTML over complex ARIA.
- Verification planning generates manual retesting steps for screen readers and keyboard navigation.
- Confidence scoring labels findings as confirmed, potential, or needing manual verification to avoid false positives.
How it works
- Submit artifacts such as component code, lighthouse reports, or UI screenshots for analysis.
- Review the audit table which summarizes issues, severity, and specific WCAG criteria.
- Implement fixes using the detailed remediation notes and stack-aware code examples provided.
Frameworks & tools
Works with any web stack including React, Vue, Angular, and Tailwind. Analyzes output from tools like Axe-core, Lighthouse, and browser DevTools.
Why this beats prompting it yourself
Generic prompts often hallucinate ARIA attributes or guess contrast ratios. This skill enforces strict evidence-based rules, distinguishing between confirmed code bugs and potential runtime issues while preventing legal-compliance hallucinations.
Use cases
- Auditing a new UI component before it hits the design system.
- Translating a raw automated scan report into prioritized developer tickets.
- Verifying accessibility during a migration from legacy code to modern frameworks.
- Preparing a remediation roadmap for a specific WCAG 2.2 AA target.
Known limitations
Cannot accurately calculate color contrast from screenshots alone. Cannot confirm dynamic runtime behavior or screen-reader output without specific manual test logs.
Cannot calculate exact contrast from images. Limited by the quality of provided HTML/logs. Does not provide legal certification.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before any payment.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 29 days ago
Permissions
No special permissions declared or detected