Skip to content
TrustedSkillsbeta
Back to all skills

Fixing Accessibility

Checked
ibelick·vlatest·frontend·MIT

This skill automatically fixes common accessibility issues in content, ensuring wider reach and usability for all users.

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 ibelick/ui-skills --skill fixing-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

ibelick

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 ibelick/ui-skills at f2264c3021.

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

Commit
f2264c3021
Manifest
skills/fixing-accessibility/SKILL.md
Scanned
1 file, 134 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 fixing-accessibility skill helps identify and resolve accessibility issues in web interfaces. It scans HTML, CSS, and JavaScript to detect problems such as missing alt text on images, improper contrast ratios, or keyboard navigation failures. The tool then provides actionable suggestions for remediation.

When to use it

  • You're auditing a website for compliance with WCAG standards.
  • A user reports difficulty navigating your site using screen readers.
  • You want to ensure your web application is accessible to people with disabilities.

Key capabilities

  • Detects common accessibility violations in HTML and CSS
  • Suggests fixes for contrast, focus management, and semantic structure
  • Analyzes keyboard navigation flow and interactive elements

Example prompts

  • "Check this webpage for accessibility issues and suggest fixes."
  • "Fix the alt text on all images that are missing descriptions."
  • "Analyze the contrast ratio of text on this page and recommend improvements."

Tips & gotchas

  • Ensure your HTML is valid before running the tool, as invalid markup can lead to false positives.
  • This skill works best when used in conjunction with manual testing for a complete accessibility review.