Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIDeepSeekDeepSeekMuseMuse+22 more

    Frontend Accessibility Reviewer

    1

    Audit HTML, CSS, and JS for WCAG compliance with actionable, copy-paste code fixes for accessibility gaps.

    Free

    10 usesSecurity scanned
    Frontend Accessibility Reviewer

    Frontend Accessibility Reviewer

    Example session with this skill installed

    Audit this React component for accessibility: Login and the CSS: .login-btn:focus { outline: none; }
    • Read your context and instructions
    • Compiled the frontend accessibility reviewer

    I have completed the accessibility audit for the login component. It currently fails several WCAG AA requirements regarding interactivity and focus visibility.

    [Frontend Accessibility Audit Report]

    🚨 Critical Issues (Must Fix):

    Non-semantic Interactivity: A div is used for a login action. Screen readers will not identify this as a clickable element, and it is not reachable via keyboard.

    Missing Keyboard Support: The element lacks a tabindex, meaning keyboard-only users cannot navigate to the login trigger.

    ⌨️ Keyboard & Focus Check:

    Focus Outline Hidden: The CSS explicitly removes the focus outline (outline: none), which is a WCAG failure. Users navigating via Tab will have no visual indicator of where they are.

    • Tab Order: Element is currently excluded from the tab sequence.

    🎨 Color & Visual Check:

    • Visual state relies on the user knowing the div is a button without standard browser styling or roles.

    🛠️ Specific Fixes Required:

    Change this:

    <div className="login-btn" onClick={handleLogin}>Login</div>
    

    To this:

    <button type="button" className="login-btn" onClick={handleLogin}>Login</button>
    

    Change this:

    .login-btn:focus { outline: none; }
    

    To this:

    .login-btn:focus { 
      outline: 2px solid #005fcc; 
      outline-offset: 2px; 
    }
    

    [Self-Check]

    • Semantic HTML violations identified
    • Keyboard navigation and focus states audited
    • Color contrast and visual reliance checked
    • Exact, copy-paste-ready code fixes provided

    Next steps

    • Replace the div with a semantic button to inherit native keyboard behavior.
    • Update the global or component-level CSS to ensure focus rings are never suppressed.
    • Test the login flow using only the Tab and Enter keys.

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

    About this skill

    The problem

    Web accessibility is often an afterthought, leading to legal risks and excluded users. Manual WCAG audits are time-consuming and generic automated tools often miss logical errors like keyboard traps or non-semantic interactive elements.

    What it does

    • Identifies non-semantic HTML like div-based buttons that break assistive technology.
    • Detects missing ARIA labels, descriptive alt text, and form-label associations.
    • Audits CSS for focus state visibility and color contrast violations.
    • Analyzes keyboard navigation logic to prevent focus traps in modals and menus.
    • Generates copy-paste code snippets to remediate identified issues immediately.

    Frameworks & tools

    Works with HTML5, CSS3, Tailwind CSS, React, Vue, and Angular components. Follows WCAG 2.1 AA standards.

    Why this beats prompting it yourself

    Generic LLMs often give vague advice like "improve your contrast." This skill is hard-coded to provide exact attribute changes and CSS overrides, ensuring you don't just know what is wrong, but have the specific code to fix it.

    Use cases

    • Pre-launch audit of new UI components or landing pages.
    • Refactoring legacy codebases to meet legal accessibility requirements.
    • Debugging reported navigation issues for screen reader users.

    Known limitations

    Cannot visually "see" rendered contrast without provided hex codes. Audit is limited to the code context provided in the session.

    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.

    Requires hex codes for contrast analysis. Cannot simulate dynamic screen reader behavior without component source code.

    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

    10 uses

    Times used to date

    Free to use

    No account required to browse

    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

    This skill performs deep audits of your HTML, CSS, and JS to detect WCAG 2.1 AA violations, such as non-semantic elements and keyboard traps, providing immediate copy-paste code fixes rather than generic advice.

    It is compatible with standard HTML5/CSS3 and popular modern frameworks like React, Vue, Angular, and Tailwind CSS, making it versatile for both legacy and modern tech stacks.

    You will receive full access to the AI skill, which includes the specialized logic for identifying complex logical errors and generating optimized remediation snippets.

    Simply provide the relevant code snippets—such as a component file or CSS stylesheet—directly to your AI agent, and the skill will automatically begin its step-by-step audit and remediation process.

    While the skill is highly accurate for code-based audits, it relies on your provided hex codes for color contrast and cannot 'see' visual elements that are not represented in the code you share.

    Yes, the skill is periodically updated to reflect the latest WCAG guidelines and best practices in frontend development, ensuring your code remains compliant with evolving standards.

    New in Frontend & Web Apps

    Free