Skip to content
TrustedSkillsbeta
Back to all skills

Accessibility

Checked
addyosmani·vlatest·frontend·MIT

This skill provides detailed descriptions of images for visually impaired users, enhancing content accessibility and inclusivity.

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 addyosmani/web-quality-skills --skill 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

addyosmani

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 addyosmani/web-quality-skills at afa8da9421.

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

Commit
afa8da9421
Manifest
skills/accessibility/SKILL.md
Scanned
3 files, 819 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 skill helps ensure that digital products are usable by people with a wide range of abilities, including those who use assistive technologies like screen readers. It provides guidance on implementing proper semantic HTML, keyboard navigation, and ARIA attributes to improve web accessibility standards.

When to use it

  • When developing or auditing a website for compliance with WCAG (Web Content Accessibility Guidelines)
  • When designing interfaces that need to be accessible to users with visual, auditory, motor, or cognitive impairments
  • When preparing content for public-facing platforms that require inclusive design practices

Key capabilities

  • Identifies and suggests fixes for common accessibility issues
  • Provides best practices for semantic HTML structure
  • Offers guidance on implementing ARIA roles and attributes properly
  • Ensures keyboard navigation is fully functional

Example prompts

  • "Check this webpage for accessibility issues and suggest improvements."
  • "How can I make my form more accessible to screen reader users?"
  • "What are the best practices for labeling buttons and interactive elements?"

Tips & gotchas

  • Always test with real assistive technologies or tools like axe or Lighthouse for accurate results.
  • Accessibility is not a one-time task; it requires ongoing maintenance as content and features evolve.