Skip to content
TrustedSkillsbeta
Back to all skills

Frontend Accessibility

Checked
aj-geddes·vlatest·frontend·MIT

Analyzes frontend code for accessibility issues (WCAG compliance), suggesting fixes for improved user experience.

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 frontend-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

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/frontend-accessibility/SKILL.md
Scanned
7 files, 485 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 frontend-accessibility skill empowers AI agents to generate, audit, and remediate web code for WCAG compliance. It ensures interfaces are navigable via keyboard, screen readers, and assistive technologies while maintaining semantic HTML structure.

When to use it

  • Initial Scaffolding: Generate accessible boilerplate HTML/CSS/JS for new landing pages or dashboards.
  • Compliance Audits: Analyze existing codebases to identify missing ARIA labels, insufficient color contrast, or improper heading hierarchies.
  • Remediation: Automatically rewrite non-compliant snippets to meet specific WCAG 2.1 Level AA standards.
  • Testing Support: Create test cases for screen reader compatibility and keyboard-only navigation flows.

Key capabilities

  • Generates semantic HTML5 structures with correct ARIA roles and states.
  • Audits color contrast ratios against WCAG guidelines.
  • Identifies missing alt text for images and non-text content.
  • Ensures logical tab order and focus management in interactive components.
  • Produces CSS that supports reduced-motion preferences.

Example prompts

  • "Audit this React component for accessibility issues and provide a list of violations with line numbers."
  • "Generate a fully accessible navigation bar using semantic HTML and ARIA landmarks for a dark-mode site."
  • "Rewrite this form to ensure all inputs have associated labels, error messages are announced by screen readers, and focus is managed correctly on submission."

Tips & gotchas

  • This skill focuses on output generation and code analysis; it does not replace manual testing with real assistive technology.
  • Always verify that generated ARIA attributes align with the actual behavior of the interactive elements to avoid confusion for users relying on screen readers.