Skip to content
TrustedSkillsbeta
Back to all skills

Frontend Accessibility Best Practices

Checked
sergiodxa·vlatest·frontend·MIT

Helps with frontend development, best practices as part of agent workflows workflows.

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 sergiodxa/agent-skills --skill frontend-accessibility-best-practices -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

sergiodxa

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 sergiodxa/agent-skills at 40e21b4618.

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

Commit
40e21b4618
Manifest
skills/frontend-accessibility-best-practices/SKILL.md
Scanned
8 files, 1,029 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 skill equips AI agents with the knowledge to implement frontend accessibility standards, ensuring web applications are usable by people with diverse abilities. It guides the creation of interfaces that comply with WCAG guidelines through semantic HTML and assistive technology support.

When to use it

  • Building new web applications where inclusive design is a primary requirement from the start.
  • Auditing existing codebases to identify and remediate accessibility barriers for screen reader users.
  • Generating component libraries or templates that adhere to best practices for color contrast and focus management.
  • Creating documentation or training materials for development teams on maintaining accessible standards.

Key capabilities

  • Semantic HTML structure generation
  • WCAG compliance guidance
  • Screen reader compatibility optimization
  • Keyboard navigation implementation
  • Color contrast verification strategies
  • ARIA attribute usage recommendations

Example prompts

"Generate a React component for a data table that fully supports screen readers and keyboard navigation." "Audit this HTML snippet for accessibility issues and suggest specific fixes to meet WCAG AA standards." "Create a style guide ensuring sufficient color contrast ratios for text elements on light and dark backgrounds."

Tips & gotchas

Always test generated code with actual assistive technologies like screen readers, as theoretical compliance does not guarantee real-world usability. Prioritize semantic HTML over complex ARIA attributes to maintain simplicity and robustness across different browsers.