Skip to content
TrustedSkillsbeta
Back to all skills

Screen Reader Testing

Checked
wshobson·vlatest·frontend·MIT

Automates accessibility screen reader testing, identifying issues like missing alt text and improper heading structure.

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 screen-reader-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

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/accessibility-compliance/skills/screen-reader-testing/SKILL.md
Scanned
1 file, 503 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 screen-reader-testing skill enables AI agents to simulate and evaluate how well web interfaces are accessible to users who rely on screen readers. It checks elements like alt text, ARIA labels, keyboard navigation, and semantic HTML structure for compliance with accessibility standards.

When to use it

  • Testing a website or application for WCAG (Web Content Accessibility Guidelines) compliance before launch
  • Debugging inaccessible UI components during development
  • Ensuring that all interactive elements are navigable via keyboard and announced properly by screen readers
  • Validating that form fields, buttons, and links have appropriate labels for users with visual impairments

Key capabilities

  • Simulates common screen reader interactions
  • Identifies missing or incorrect ARIA attributes
  • Checks for proper semantic HTML usage
  • Verifies keyboard navigation flow

Example prompts

  • "Test the homepage for accessibility using a screen reader simulation."
  • "Check if all buttons on this page have descriptive ARIA labels."
  • "Run a screen reader test on the login form to ensure it's accessible."

Tips & gotchas

  • Ensure that your website is fully loaded and interactive before running tests.
  • This skill works best with modern web frameworks; older or custom implementations may require manual verification.