Skip to content
TrustedSkillsbeta
Back to all skills

Accessibility Testing

Checked
aj-geddes·vlatest·frontend·MIT

Automates WCAG compliance checks, identifies accessibility issues in web content, and suggests remediation steps.

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 aj-geddes/useful-ai-prompts --skill accessibility-testing -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

aj-geddes

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 aj-geddes/useful-ai-prompts at 3f5182cfd7.

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

Commit
3f5182cfd7
Manifest
skills/accessibility-testing/SKILL.md
Scanned
9 files, 609 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

The accessibility-testing skill enables AI agents to evaluate web interfaces for compliance with WCAG standards, identifying barriers that prevent users with disabilities from accessing digital content effectively. It automates the detection of missing alt text, poor color contrast, and semantic HTML errors to ensure inclusive design.

When to use it

  • Before launching a public website to verify compliance with legal accessibility requirements like Section 508 or ADA.
  • During the development cycle to catch accessibility issues early in the UI/UX design phase.
  • When auditing third-party libraries or components for potential exclusionary patterns.
  • To generate an initial report of accessibility gaps before conducting manual user testing.

Key capabilities

  • Scans HTML and CSS for WCAG 2.1 guideline violations.
  • Detects missing alternative text on images and non-text content.
  • Analyzes color contrast ratios against defined thresholds.
  • Identifies improper heading structures and form label associations.
  • Flags keyboard navigation traps and focus order issues.

Example prompts

"Analyze this React component code for WCAG 2.1 Level AA violations and list specific fixes." "Scan the provided HTML page for missing alt attributes and low color contrast issues." "Generate a checklist of accessibility improvements needed for this landing page to pass an automated audit."

Tips & gotchas

Automated tools cannot fully replicate human perception; always follow up with manual testing involving screen readers and keyboard-only navigation. Ensure your AI agent has access to the full source code or live URL context to provide accurate analysis.