Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    accessibility reviewer

    1

    Audit UI components and markup for WCAG 2.2 compliance with actionable fix recommendations.

    $6

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned
    accessibility reviewer

    accessibility reviewer

    Example session with this skill installed

    Audit this button component for WCAG 2.1 AA compliance: Submit. It has a blue background #0000FF and white text.
    • Read your context and instructions
    • Compiled the accessibility reviewer

    I have reviewed the provided button component for WCAG 2.1 AA compliance. The implementation relies on a generic div which lacks native interactive properties.

    Accessibility Review Report

    IDStatusPage/state/elementUser impactSeverityEvidence/reproductionWCAG criterionFixRetest
    A11Y-01ConfirmedSubmit ButtonKeyboard users cannot trigger actionCriticalComponent uses a div; not in tab order; no KeyDown listener2.1.1 (A)Change div to <button> or add tabindex="0" and keyboard listenersAttempt to trigger button using 'Enter' and 'Space'
    A11Y-02ConfirmedSubmit ButtonScreen reader users miss roleMajorRole="button" is present but lacks focusable state4.1.2 (A)Use native <button> elementVerify screen reader announces "Submit, button"
    A11Y-03PotentialSubmit ButtonLow vision users may struggle with contrastMinorBlue #0000FF and White #FFFFFF is 8.59:1 (Passes AA)1.4.3 (AA)None required for AAVerify contrast in high-contrast mode

    Remediation Snippet

    // Problematic Code
    <div role="button" onclick="submit()">Submit</div>
    
    // Corrected Code
    <button type="button" onClick={submit}>Submit</button>
    

    Manual Test Scenario

    Keyboard Test: Use the Tab key to navigate the page. Ensure the focus ring lands on the "Submit" button. Press 'Enter' to trigger the function.
    2.

    Screen Reader Test: Navigate to the element using a screen reader (NVDA/VoiceOver). Confirm it is announced as a "button" and the label "Submit" is read clearly.

    Next steps

    1. Replace the div with a native button element to inherit global attributes.
    2. Verify the focus indicator is visible when the button is focused.
    3. Integrate an automated linter to catch non-semantic button usage in the future.

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

    About this skill

    Accessibility debt and WCAG violations often go unnoticed until a legal audit or a blocked user report. This skill provides a systematic review of UI components and markup to catch barriers before they reach production.

    What it does

    • Analyze markup Inspects HTML or JSX for semantic roles, names, values, and heading hierarchies.
    • Identify barriers Detects keyboard focus traps, illogical tab orders, and missing ARIA properties.
    • Contrast verification Checks text and non-text contrast against AA or AAA thresholds.
    • Screen reader simulation Predicts AT announcements for dynamic content and live regions.
    • Actionable remediation Provides specific code fixes and step-by-step retest scenarios.

    How it works

    1. Define scope Identify the specific pages, states, and user flows requiring audit.
    2. Execute inspection Review semantic roles, landmarks, and interaction feedback.
    3. Map violations Align findings to specific WCAG 2.2 criteria and conformance levels.
    4. Generate report Produce a structured table including severity, evidence, and code fixes.

    Frameworks & tools

    Works with any web-based stack including React, Vue, Angular, and plain HTML. It references WCAG 2.1/2.2 success criteria and supports evaluation for screen readers and keyboard-only navigation.

    Why this beats prompting it yourself

    Generic prompts often miss interactive states like focus management in dialogs or dynamic live region updates. This skill follows a rigorous 7-step procedure that forces a distinction between confirmed failures and potential barriers, ensuring you don't receive false conformance claims from automated-only checks.

    Use cases

    • Component Audits Reviewing a new UI library component before it is merged into the design system.
    • Release Checks Running a final accessibility pass on a critical user flow like checkout or registration.
    • Bug Remediation Investigating reported accessibility issues and generating reproducible fix scenarios.
    • Compliance Mapping Documenting how specific interface elements meet (or fail) WCAG success criteria.

    Known limitations

    Cannot verify DOM or runtime behavior from visual-only artifacts. It does not provide legal conclusions or absolute conformance guarantees.

    Cannot verify DOM or runtime behavior from visual-only artifacts. Requires human review to establish WCAG conformance. Does not provide legal conclusions.

    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

    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 2 days ago

    Permissions

    Write Files
    Listed2 days ago

    What's inside

    Frequently Asked Questions

    The skill supports all web-based frameworks including React, Vue, and Angular. As long as you can provide the HTML, JSX, or component markup, the agent can perform a deep semantic and structural audit.

    Unlike generic prompts that might miss hidden interaction states, this skill uses a specialized 7-step procedure to test focus management, ARIA live regions, and keyboard traps. It distinguishes between definite WCAG failures and potential barriers that require human verification.

    The skill outputs a structured report containing a severity-ranked table of violations, the specific WCAG 2.2 criteria triggered, and actionable code snippets to fix each identified issue.

    While the skill is highly effective at identifying barriers in code and markup, it cannot interact with live runtime environments or provide legal certifications. It is a remediation and auditing tool designed to catch issues before they reach a legal auditor.

    Yes, the skill is specifically designed to handle complex components like modals, dropdowns, and tabs, ensuring that keyboard focus is managed correctly and screen reader announcements are triggered during state changes.

    New in Testing & Debugging