Skip to content
TrustedSkillsbeta
Back to all skills

Accessibility Compliance

Checked
wshobson·vlatest·frontend·MIT

Ensures digital content meets accessibility standards (WCAG) for inclusivity and legal compliance, minimizing risk & broadening user reach.

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 wshobson/agents --skill accessibility-compliance -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

wshobson

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 wshobson/agents at 46891e7e60.

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

Commit
46891e7e60
Manifest
plugins/ui-design/skills/accessibility-compliance/SKILL.md
Scanned
5 files, 2,060 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

The accessibility-compliance skill ensures that digital content, such as websites and applications, meets established standards like WCAG (Web Content Accessibility Guidelines). It identifies potential barriers to access for users with disabilities and provides actionable recommendations to improve compliance.

When to use it

  • Before launching a new website or application to ensure it is accessible to all users.
  • When updating existing content to meet evolving accessibility regulations.
  • During audits to evaluate the current level of accessibility compliance.
  • To prepare materials for public-facing platforms that require ADA (Americans with Disabilities Act) compliance.

Key capabilities

  • Scans digital content for common accessibility issues.
  • Provides detailed reports on non-compliant elements.
  • Offers suggestions for remediation based on WCAG guidelines.
  • Supports multiple standards and regulations globally.

Example prompts

  • "Check this webpage for accessibility issues."
  • "Generate a compliance report for our mobile app according to WCAG 2.1."
  • "Identify any barriers to screen reader users in this document."

Tips & gotchas

  • Ensure that the content being checked is fully rendered and accessible to the tool.
  • Use this skill in conjunction with manual testing for comprehensive results.