Skip to content
TrustedSkillsbeta
Back to all skills

Web Accessibility

Checked
hoodini·vlatest·frontend

Automatically identifies and fixes common web accessibility issues (WCAG) on frontend code.

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 hoodini/ai-agents-skills --skill web-accessibility -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

hoodini

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 hoodini/ai-agents-skills at f7a43d8f85.

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

Commit
f7a43d8f85
Manifest
skills/web-accessibility/SKILL.md
Scanned
1 file, 202 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 enables AI agents to analyze and improve the accessibility of web pages, ensuring digital content is usable for everyone. It specifically targets frontend code to identify barriers that prevent users with disabilities from interacting effectively with websites.

When to use it

  • Auditing existing React or Vue components for WCAG compliance before deployment.
  • Generating automated reports on color contrast ratios and ARIA attribute usage.
  • Refactoring HTML structures to support screen readers and keyboard navigation.
  • Validating forms and interactive elements against accessibility standards.

Key capabilities

  • Frontend code scanning for common accessibility violations.
  • Analysis of semantic HTML structure and ARIA implementation.
  • Identification of issues affecting screen reader compatibility.
  • Detection of insufficient color contrast in UI elements.

Example prompts

  • "Scan this React component file and list all missing ARIA labels."
  • "Generate a report on accessibility violations in this HTML form."
  • "Refactor this navigation menu to ensure full keyboard navigability."

Tips & gotchas

Ensure the AI agent has access to the specific frontend source code or live URL it needs to audit. While this skill identifies issues, manual testing with actual assistive technologies like screen readers is still recommended for final validation.