a11y root cause

    1

    Identify and fix the specific source components responsible for the majority of your app's accessibility violations.

    Free

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    a11y root cause

    Example session with this skill installed

    Run an a11y audit on my React app at localhost:3000 for the routes in routes.txt and tell me which components to fix first.

    • Read your context and instructions
    • Compiled the a11y root cause
    • Generated the document

    I have completed the accessibility scan of 8 routes. By clustering 142 violations, I identified that 65% of your accessibility debt originates from just 3 shared components.

    Accessibility Leverage Report

    ComponentSource FileViolationsRulesImpact
    PrimaryButtonsrc/components/ui/Button.tsx54button-nameHigh (Shared)
    FormInputsrc/components/forms/Input.tsx28labelMedium (Shared)
    SidebarNavsrc/layout/Sidebar.tsx11navigation, color-contrastMedium (Local)

    Analysis

    The PrimaryButton component is missing an accessible name when used with icons. This is appearing on every page containing a data grid or header actions. Fixing this one file will resolve nearly 40% of the total audit failures.

    Recommended Fixes

    PrimaryButton: Update the component to accept an aria-label or screenReaderText prop and make it required when no children are present.
    2. FormInput: Wrap the input in a native <label> or use htmlFor to link the existing label element correctly.
    3.

    Color Contrast: The Sidebar background #f4f4f4 fails against white text. I recommend updating the theme variable $nav-bg to #222.

    Next steps

    1. I can start applying the fix to src/components/ui/Button.tsx and updating its 12 callers.
    2. Shall I generate a storageState.json to scan the authenticated /dashboard routes?
    3. Review the a11y-report/report.md for the full breakdown of markup snippets.

    Button.tsx

    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

    Fixing accessibility issues one by one in a large frontend app is a losing game. A single bug in a shared component often creates hundreds of violations across the entire site. This skill shifts your focus from individual page errors to the source components that generate them.

    What it does

    • Root cause attribution maps every axe-core violation back to the specific React, Vue, or Angular component file in your source code.
    • Leverage ranking generates a table showing which components are responsible for the highest volume of issues across your app.
    • Automated scanning uses Playwright to crawl your local dev server and catch violations in real-time rendered states.
    • Guided refactoring applies fixes to shared components using native HTML patterns and ARIA standards.
    • Verification loops runs post-fix scans to calculate the exact percentage of debt removed and catch any regressions.

    How it works

    1. Targeting: You provide a list of local URLs and ensure the app is running in development mode to allow for source attribution.
    2. Scan & Cluster: The tool runs an axe-core audit via Playwright and clusters the findings by component file path.
    3. Audit Analysis: It analyzes the leverage report to identify "high-impact" components where a single change fixes multiple pages.
    4. Implementation: It applies fixes to component markup or styles, or updates component APIs to enforce accessible props.
    5. Validation: A second scan compares the new state against the baseline to prove the fix and verify compliance.

    Frameworks & tools

    Works with React, Vue, and Angular applications running on Vite, Webpack, or framework-specific CLIs. It uses Playwright for browser automation and axe-core for accessibility testing.

    Why this beats prompting it yourself

    Generic prompts often suggest fixing the output HTML, which you then have to manually trace back to your source. This skill automates the trace-to-source logic and prioritizes your workload by impact, ensuring you do not waste time on low-leverage "local" fixes when a "shared" fix is possible.

    Use cases

    • Audit a legacy frontend codebase for WCAG 2.1/2.2 compliance.
    • Clean up "noisy" Lighthouse reports by fixing root component bugs.
    • Update a shared design system or component library to meet accessibility standards.
    • Enforce required accessibility props across a large engineering team.

    Known limitations

    Requires the application to be running in development mode for component attribution. It cannot audit native mobile apps or static HTML files without a server.

    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.

    Requires dev mode for attribution. No native mobile or static HTML support. Automated scans only catch a subset of WCAG issues; manual testing is still required for focus and screen readers.

    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 1 day ago

    • Free with an Agensi account

    Software
    PlaywrightNode.js

    Permissions

    Terminal / Shell
    Browser
    Read Files
    Listed1 day ago

    What's inside

    Frequently Asked Questions

    Traditional scanners list individual DOM errors, but this skill traces those errors back to the specific React, Vue, or Angular component file causing them, allowing you to fix hundreds of errors with a single code change.

    The skill requires your application to be running in development mode (e.g., via Vite or Webpack) so it can accurately map browser-rendered violations to your local source code paths.

    This skill is designed for any AI agent that has file-system access and a browser execution environment, such as those built on Playwright or similar automation frameworks.

    While it identifies and suggests fixes for high-impact components, you retain full control to review and approve every code change before it is committed to your repository.

    The purchase includes the core logic for root cause attribution, the leverage-ranking reporting module, and the automated Playwright-to-Axe integration workflow.

    Yes, it is specifically optimized for shared component libraries and design systems where a single change to a base component (like a Button or Input) propagates fixes across the entire application.

    New in Testing & Debugging

    Free