Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Accessibility Audit Commander

    1

    Structured WCAG 2.2 accessibility audits with severity-ranked findings and specific code fixes.

    Free

    6 uses5.0 (1 review)
    Accessibility Audit Commander

    Accessibility Audit Commander

    Example session with this skill installed

    Audit the accessibility of this React modal component: XSettings
    • Read your context and instructions
    • Compiled the accessibility audit commander

    The audit of the React modal component is complete. This component has 1 Blocker and 2 Critical issues that prevent keyboard and screen reader users from successfully managing settings.

    Accessibility Audit Report: Settings Modal

    Scope: React Modal Component (inline snippet)
    Summary: 1 Blocker, 2 Criticals, 0 Warnings. The component is currently inaccessible to keyboard-only and screen reader users due to a lack of focus management and missing labels.

    Findings

    IDSeverityWCAG CriterionLocationWhat's wrongAffected Users
    A11Y-001Blocker2.4.3 Focus Orderdiv.modalFocus is not trapped inside the modal when open.Keyboard, Screen Reader
    A11Y-002Critical3.3.2 Labels or InstructionsinputInput relies on placeholder text instead of a label.Screen Reader, Cognitive
    A11Y-003Critical4.1.2 Name, Role, ValuebuttonThe close button has no accessible name, only a visual 'X'.Screen Reader
    Remediation Code

    Fix for A11Y-002 (Missing Label):

    // Before
    <input type="text" placeholder="Username" />
    
    // After
    <label htmlFor="username">Username</label>
    <input id="username" type="text" placeholder="e.g. jdoe74" />
    

    Fix for A11Y-003 (Accessible Name):

    // Before
    <button onClick={open}>X</button>
    
    // After
    <button onClick={close} aria-label="Close settings modal">X</button>
    

    Remediation order

    1. Implement a focus trap using a library or useEffect to prevent keyboard users from tabbing into the background (A11Y-001).
    2. Add the aria-label to the close button so screen reader users know how to exit (A11Y-003).
    3. Replace placeholders with proper <label> elements for form persistence (A11Y-002).

    Next steps

    • Apply the focus trap logic to the modal container.
    • Update the button and input JSX with the provided snippets.
    • Verify the fix by tabbing through the open modal.

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

    About this skill

    Development teams often treat accessibility as a post-launch afterthought or a vague checklist. This skill runs a structured WCAG 2.2 audit directly on your frontend code, components, or live pages to find blockers before they reach production. It moves beyond generic advice by providing specific code-level fixes and ranking issues by their actual impact on users with assistive technology.

    What it does

    • Multi-pass auditing — Reviews interfaces through four distinct lenses: semantics, keyboard interaction, visual perception, and robustness.
    • Severity ranking — Categorizes issues as Blocker, Critical, Warning, or Note based on how they impact real user tasks.
    • Code-level remediation — Delivers exact code changes and ARIA implementations rather than general accessibility theory.
    • Contrast verification — Uses a contrast checker to validate hex values against 4.5:1 and 3:1 WCAG thresholds.
    • Assistive tech simulation — Evaluates how components behave for screen readers, keyboard-only users, and motion-sensitive users.

    How it works

    1. Define scope — Identify the specific component, page, or code block that requires an audit.
    2. Execute audit passes — The agent runs a structured four-pass check starting with DOM semantics and ending with ARIA robustness.
    3. Analyze findings — Issues are mapped to specific WCAG 2.2 criteria and severity levels.
    4. Generate report — Receive a structured remediation plan including IDs, locations, and before/after code snippets.

    Frameworks & tools

    This skill works with any frontend stack including React, Vue, Svelte, and vanilla HTML/CSS. It utilizes scripts/contrast-checker.py for color analysis and references the WCAG 2.2 standard.

    Why this beats prompting it yourself

    Generic prompts often return vague "best practices" or hallucinate ARIA attributes. This skill follows a rigid four-pass framework and requires specific remediation code, ensuring you get actionable PR feedback instead of a generic checklist.

    Use cases

    • Pre-PR audits — Review a new UI component for keyboard traps and semantic errors before merging.
    • Design system hardening — Audit core library components to ensure accessibility scales across the entire product.
    • Compliance reporting — Generate a structured WCAG 2.2 status report for stakeholders or legal teams.
    • Fixing broken UX — Identify why a specific form or modal is failing for screen reader users.

    Known limitations

    Audits are limited to the specific code or live scope provided. Script-based contrast checking requires raw hex values to be present in the source or provided manually.

    Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Frontend & Web Apps.

    Audits are scope-specific and do not cover entire sites unless all code is provided. Contrast checking requires explicit hex values. Logic ignores CSS-in-JS if values are generated at runtime.

    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

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

    This skill has been used 6 times.

    Trust & safety

    Security scan

    Security scan passed 24 days ago

    • Free with an Agensi account

    Software
    Python

    Permissions

    No special permissions declared or detected

    Listed24 days ago

    What's inside

    Frequently Asked Questions

    The skill performs a structured four-pass audit (semantics, keyboard, visual, and robustness) on your frontend code to identify WCAG 2.2 violations and provide specific, copy-pasteable code fixes.

    It is framework-agnostic and works with any frontend stack, including React, Vue, Svelte, and vanilla HTML/CSS, provided it can access the component code or DOM structure.

    No, this skill functions as a logic layer for your AI agent; simply provide the code snippet, component file, or page structure you want audited to begin the process.

    Each finding is ranked by severity (Blocker, Critical, Warning, or Note), allowing development teams to prioritize fixes based on their actual impact on users with assistive technology.

    While the skill includes a contrast checker for hex values, it cannot 'see' images or complex CSS gradients unless the raw color data is provided in the code or prompt.

    Your purchase includes the structured audit logic and remediation framework, which is updated periodically to reflect the latest WCAG 2.2 success criteria and ARIA best practices.

    New in Frontend & Web Apps

    Free