Skip to content
TrustedSkillsbeta
Back to all skills

Accessibility Auditor

Checked
patricio0312rev·vlatest·frontend·MIT

This Accessibility Auditor skill analyzes web content to identify potential accessibility issues, ensuring a more inclusive user experience for everyone.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add patricio0312rev/skills --skill accessibility-auditor -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

patricio0312rev

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned patricio0312rev/skills at 79ea6af485.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
79ea6af485
Manifest
frontend/accessibility-auditor/SKILL.md
Scanned
1 file, 758 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill acts as an automated accessibility auditor, scanning web interfaces to identify barriers that prevent users with disabilities from accessing content. It evaluates elements against standard compliance criteria to ensure digital products are inclusive and usable by everyone.

When to use it

  • Before launching a new website or updating existing pages to verify WCAG compliance.
  • During development sprints to catch accessibility issues early in the frontend workflow.
  • When generating audit reports for stakeholders requiring proof of inclusive design practices.
  • To validate that recent CSS or HTML changes have not introduced new usability barriers.

Key capabilities

  • Scans web interfaces for common accessibility violations.
  • Identifies specific elements causing barriers for users with disabilities.
  • Provides actionable feedback based on established compliance standards.

Example prompts

  • "Run an accessibility audit on the homepage and list all critical errors found."
  • "Check if the navigation menu meets WCAG 2.1 guidelines for keyboard users."
  • "Generate a report highlighting color contrast issues in the footer section."

Tips & gotchas

Ensure the target web interface is fully loaded before running the audit to avoid false negatives on dynamic content. This tool focuses on frontend elements, so it may not detect backend logic errors affecting accessibility.