More screenshots

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Accessibility Compliance Agent

    2

    Audits HTML/React/Next.js code against WCAG 2.1/2.2 AA, fixes it, and generates a client-ready compliance report.

    Free

    19 uses5.0 (1 review)
    Accessibility Compliance Agent

    Accessibility Compliance Agent

    Example session with this skill installed

    Can you audit this React checkout form for WCAG 2.1 AA accessibility issues and give me the fixed code plus a report I can send to my client?

    export default function CheckoutForm() {
      return (
        <div>
          <div>Email</div>
          <input type="text" />
          <div>Card Number</div>
          <input type="text" style={{border: '1px solid red'}} />
          <div onClick={handleSubmit}>Submit</div>
        </div>
      );
    }
    
    • Read your context and instructions
    • Compiled the accessibility compliance agent
    • Generated the document

    I audited CheckoutForm.jsx against WCAG 2.1 Level AA and found 4 issues — 2 critical, 1 moderate, 1 minor. The critical issues would block keyboard and screen-reader users from completing checkout entirely. Fixed code and full report below.

    FIXED CODE

    export default function CheckoutForm() {
      return (
        <form onSubmit={handleSubmit}>
          <label htmlFor="email">Email</label>
          <input id="email" type="email" required />
    
          <label htmlFor="card">Card Number</label>
          <input
            id="card"
            type="text"
            aria-invalid="true"
            aria-describedby="card-error"
          />
          <span id="card-error" role="alert">
    
        Card number format looks invalid
    
          </span>
    
          <button type="submit">Submit</button>
        </form>
      );
    }
    

    COMPLIANCE REPORT
    Target: WCAG 2.1 AA | Scope: CheckoutForm.jsx | Framework: React

    [CRITICAL] Unlabeled inputs (1.3.1, 4.1.2)
    Screen readers announced "edit text, blank" with no indication of what to enter. Fixed with associated <label> elements via htmlFor/id.

    [CRITICAL] Non-interactive Submit control (2.1.1, 4.1.2)
    A <div onClick> is invisible to keyboard users and unannounced to screen readers. Replaced with a native <button type="submit"> inside a <form>.

    [MODERATE] Error state conveyed by color alone (1.4.1)
    A red border alone doesn't reach colorblind or low-vision users. Added aria-invalid and a visible, programmatically linked error message.

    [MINOR] Input missing type semantics
    Email field used type="text" instead of type="email", losing built-in validation and mobile keyboard optimization.

    NEEDS MANUAL VERIFICATION
    Actual rendered contrast ratio of the error text color, and a real screen-reader pass (VoiceOver/NVDA) to confirm announcement order.

    NEXT STEPS

    1. Drop the fixed code into your component and re-test the form flow.
    2. Run axe DevTools or Lighthouse for an automated cross-check.
    3. Do one manual pass with a screen reader before shipping to the client.

    CheckoutForm.jsx

    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

    Turns any frontend code into (1) an accessibility-fixed version and (2) a compliance report you can hand straight to a client, manager, or auditor.

    Why this matters right now: the EU Accessibility Act became enforceable in June 2025, and US ADA Title II requires state/local government sites to meet WCAG 2.1 AA on a rolling schedule through 2027. Agencies and freelance devs are under real, dated pressure to prove compliance — not just "be more accessible" in the abstract.

    What it does

    • Works across HTML, JSX/React, and Next.js App Router code
    • Audits 8 categories: images/alt text, semantic structure & headings, forms & labels, ARIA usage, keyboard navigation & focus, color contrast, media captions, motion/animation
    • Every issue found is cited to its exact WCAG Success Criterion number and level (e.g. "2.1.1 Keyboard (A)") — no vague "improve accessibility" notes
    • Delivers fixed code alongside a severity-ranked report (Critical / Moderate / Minor), plus an honest "needs manual verification" section for anything code review genuinely can't confirm (live contrast values, real screen-reader behavior)
    • Never claims "fully compliant" — it reports what's addressable from code, and tells you plainly what still needs a human accessibility pass

    Built for agencies doing client audits, freelance devs prepping a site for a compliance deadline, and teams who want a first-pass accessibility review before paying for a full manual audit.

    Code-level review only — not a full audit. This skill checks what's inferable from source code. It can't verify real computed color contrast (depends on final rendered styles), true keyboard-trap behavior (needs a live DOM), or actual screen-reader output (needs a real AT pass with VoiceOver/NVDA/JAWS). These are flagged as "needs manual verification," not silently assumed to pass.
    Never claims full WCAG compliance. The skill is designed to say "addresses the issues identifiable from code review," not "fully compliant" — compliance ultimately requires human + assistive-tech testing the skill can't perform itself.
    Covers HTML, JSX/React, Next.js App Router, and Vue only. No dedicated patterns yet for Angular, Svelte, native mobile (iOS/Android), or server-rendered templating languages outside these.
    Doesn't audit non-code artifacts. PDFs, embedded third-party widgets/iframes (e.g. chat widgets, payment forms you don't own), images-as-text, and video/audio caption content (vs. the presence of a captions track) are out of scope.
    WCAG 2.1 AA by default. WCAG 2.2 or AAA criteria are only applied if explicitly requested — results won't reflect those stricter/newer criteria unless asked.
    No legal guarantee. This is an engineering aid, not legal advice. It doesn't guarantee ADA Title II, EAA, or other jurisdiction-specific legal compliance — regulatory requirements vary and often require legal review alongside technical remediation.
    Static analysis of the code as given. Dynamic behavior (state changes, animations, content injected at runtime) is only as accurate as what's visible in the submitted code — runtime-only accessibility bugs may be missed.

    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 any payment.

    Reviews

    5.0
    1 review
    5
    1
    4
    0
    3
    0
    2
    0
    1
    0

    This skill has been used 19 times.

    Trust & safety

    Security scan

    Security scan passed 2 months ago

    • Free with an Agensi account

    Permissions

    No special permissions declared or detected

    Listed2 months ago

    What's inside

    Frequently Asked Questions

    The agent performs a deep audit of HTML, React, and Next.js code across eight categories, providing both accessibility-fixed code and a severity-ranked report cited to specific WCAG 2.1/2.2 Success Criteria.

    While this agent fixes programmatic issues like ARIA labels and semantic structure, it will flag items requiring human context—such as descriptive alt-text or live screen-reader testing—in a dedicated 'Manual Verification' section.

    Yes, the agent is optimized for modern frontend frameworks, including the Next.js App Router and JSX, ensuring it understands component-based architecture and React-specific accessibility patterns.

    You receive the full AI agent skill configuration, including the auditing logic and reporting templates designed to produce client-ready compliance documentation.

    This agent is designed for use within standard AI agent environments and IDE integrations; once imported, you simply provide your source files or component snippets to trigger the audit process.

    This skill is regularly updated to reflect new WCAG success criteria and evolving standards, ensuring your audits remain accurate against current legal requirements like ADA Title II.

    New in Frontend & Web Apps