Skip to content
TrustedSkillsbeta
Back to all skills

Accessibility Engineer

Checked
mae616·vlatest·frontend·MIT

This Accessibility Engineer skill helps you proactively identify and address potential website accessibility issues, ensuring inclusive design 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 mae616/design-skills --skill accessibility-engineer -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

mae616

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 mae616/design-skills at 79e3398bee.

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

Commit
79e3398bee
Manifest
skills/accessibility-engineer/SKILL.md
Scanned
1 file, 87 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

This Accessibility Engineer skill helps AI agents proactively identify and address potential website accessibility issues, ensuring inclusive design for all users. It focuses on implementing best practices related to WAI-ARIA, screen reader support, semantic HTML, keyboard navigation, and focus management within UI implementations. The goal is to create accessible experiences that are usable by assistive technologies.

When to use it

  • When designing or reviewing user interfaces with accessibility requirements.
  • To ensure compliance with accessibility standards (e.g., WAI-ARIA).
  • During the implementation of any UI element, particularly those involving buttons, links, forms, and interactive components.
  • When needing assistance with keyboard navigation and focus management.
  • For ensuring proper screen reader support.

Key capabilities

  • Prioritizes using native HTML elements over ARIA attributes whenever possible.
  • Provides guidance on creating accessible names for buttons, links, and inputs (using visible text, aria-label, or aria-labelledby).
  • Offers rules for structuring forms with proper label associations (for/id) and error communication.
  • Advises on using ARIA attributes like aria-pressed, aria-expanded, and aria-live appropriately.
  • Provides best practices for keyboard operation, focus management (including tabindex), and image/media accessibility.

Example prompts

  • "How should I make this button accessible?"
  • "What's the correct way to label an icon-only link?"
  • "I need to create a form with required fields; what ARIA attributes should I use?"
  • “Ensure keyboard navigation is logical for this UI.”

Tips & gotchas

  • Always prioritize using native HTML elements before resorting to ARIA.
  • Avoid overuse of aria-label as it can lead to redundant announcements.
  • Visible focus indicators are crucial; do not remove them.