Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Accessibility Audit: find, fix and verify

    1

    Your agent audits your site for accessibility (WCAG 2.2 A/AA) in a real browser, walks it by keyboard, fixes the issues in your source code, then re-runs the audit to prove each fix.

    Free

    Security scanned

    Accessibility Audit: find, fix and verify

    Example session with this skill installed

    Run an accessibility audit on localhost:3000, including the sign-in dialog, and fix what you find.

    • Read your context and instructions
    • Compiled the accessibility audit
    • Generated the document

    Summary

    Audited the shop page and its sign-in dialog in Chromium:

    30 issues (5 critical, 11 serious, 14 moderate), and focus was trapped inside the dialog. After the fixes, the re-run finds

    0 issues.

    Findings (before)

    SeverityIssueWCAGCount
    CriticalImages without alt text1.1.13
    CriticalSubmit button with no text4.1.21
    CriticalKeyboard trap: Tab cycles between #pass and #user and never leaves2.1.21
    SeriousText contrast 2.05:1 (needs 4.5:1)1.4.34
    Serious<html> has no lang attribute3.1.11
    SeriousIcon link with no accessible name2.4.41
    SeriousClickable divs ("Sign in", "Add to cart") can't be reached by keyboard2.1.13
    SeriousNo visible focus indicator2.4.72
    ModerateHeading levels skip, no main landmark, content outside landmarksbest practice14

    An annotated screenshot (a11y-report/page-1.png) outlines every critical and serious issue.

    Fixes made (in the source, not the build)

    • Clickable <div>s became real <button>s with specific names ("Add desk lamp to cart")
    • Sign-in dialog: removed the Tab trap, added role="dialog", labels, a Close button and Escape to close
    • Product images got alt text describing each product, and the icon link got an aria-label
    • The empty submit became a "Subscribe" button, and the email field got a real <label>
    • The muted text color went from #b5b5b5 (2.05:1) to #595959
    • Added lang="en", <header>/<nav>/<main> landmarks, h2/h3 headings, and a :focus-visible outline

    Verify

    $ npx a11y-audit-skill http://localhost:3000 --click ".top .btn"
    0 issues (0 critical, 0 serious, 0 moderate, 0 minor)
    

    Still needs a human

    Automated checks catch about a third to half of real issues. Still check: whether the alt text is actually meaningful, focus order, error messages, 200% zoom, and reduced motion.

    page-1.png

    PDF · document

    Generated

    Example file from a real run - the skill writes it into your workspace.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    AI-generated UIs ship with <div onclick> buttons, unlabeled inputs, low contrast and focus you can't see. This skill makes your coding agent catch and fix them, and verify every fix.

    What it checks

    • WCAG 2.2 A/AA rules (axe-core, 90+ rules) in real Chromium: alt text, labels, contrast, ARIA misuse, heading order, page language and more
    • Keyboard walk: it presses Tab like a keyboard-only user and flags invisible focus (2.4.7), keyboard traps (2.1.2) and mouse-only controls (2.1.1)
    • Screen-reader view: the accessibility tree, so the agent can sanity-check names, roles and landmarks
    • Interactive states: it opens dialogs, menus and drawers first, which is where keyboard traps live

    How your agent uses it

    1. Audits every important state of your page
    2. Fixes critical issues first, in your components rather than the built output, preferring native HTML over ARIA
    3. Re-runs the audit and reports before and after counts. A finding counts as fixed only when it's gone from the new report.

    It's told never to game the audit (no aria-hidden to hide findings), and never to claim your site is "fully compliant". Automated checks find about a third to half of real issues, so the report ends with what still needs a human check.

    Also included: annotated screenshots with each serious issue outlined, a Markdown and JSON report, and an exit code for CI.

    Requirements

    Node 18+. On first use the agent installs the a11y-audit-skill npm package and Chromium (one command).

    Why it matters

    The EU Accessibility Act has been enforced since June 2025, and US ADA web lawsuits run in the thousands every year.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Testing & Debugging.

    Automated audits catch ~30-50% of issues. Requires local dev server or HTML path. Does not perform form submissions or destructive actions. Human review still required for subjective criteria.

    How to use

    1. 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. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before buying a skill.

    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

    Free to use

    No account required to browse

    Trust & safety

    Security scan

    Security scan passed 16 days ago

    • Free with an Agensi account

    Software
    a11y-audit-skillNode.jsPlaywright

    Permissions

    Terminal / Shell
    Browser
    Read Files
    Write Files
    Network Access
    Listed16 days ago

    What's inside

    Frequently Asked Questions

    While standard LLMs can only review static code, this skill uses a headless browser to analyze the actual rendered DOM and accessibility tree, allowing it to detect interaction-based issues like keyboard traps and focus mismanagement that static analysis misses.

    Any web stack: React, Vue, Svelte, Angular or plain HTML. It audits the pages you point it at, either a local dev server URL or a built HTML file, and can click into dialogs and menus first to audit those states.

    The skill requires Node.js and will automatically guide the setup of Chromium via Playwright if it isn't already present in your environment to ensure it can accurately render and scan your UI.

    You receive the full agent skill configuration, including the logic for automated WCAG 2.2 auditing, keyboard navigation simulation, and visual reporting, along with instructions for integrating it into your workflow.

    It can identify 30-50% of issues including ARIA misuse, color contrast, and missing alt text, but it cannot perform manual tasks like checking for logical reading order or testing data-destructive form submissions.

    New in Testing & Debugging

    Free