Skip to content
TrustedSkillsbeta
Back to all skills

Wcag Audit Operable Target Size

Checked
jkense·vlatest·frontend·MIT

Analyzes webpage elements to ensure operable target sizes meet WCAG 2.1 Success Criterion 2.5.5.

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 jkense/agent-skills-wcag --skill wcag-audit-operable-target-size -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

jkense

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 jkense/agent-skills-wcag at 7fc6eec6ad.

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

Scanned
2 files, 295 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 assesses web page elements against WCAG success criterion 2.5.5 (Target Size) to ensure they are sufficiently large and spaced for accessibility. It determines if interactive components meet the minimum target size of 44x44 CSS pixels, which is crucial for users with motor impairments. The tool provides feedback on elements that fail this test, helping developers improve usability.

When to use it

  • Accessibility Audits: Integrate into automated website accessibility audits to proactively identify and fix issues.
  • Design Reviews: Use during the design phase of a website or application to ensure interactive elements are designed with accessibility in mind.
  • Usability Testing: Employ as part of usability testing, especially when evaluating designs for users with motor impairments.
  • Remediation Efforts: Apply after receiving user feedback regarding difficulty interacting with page elements.

Key capabilities

  • Evaluates interactive components against WCAG 2.5.5 target size requirements.
  • Identifies elements smaller than the recommended 44x44 CSS pixel dimensions.
  • Provides feedback on spacing between interactive elements.

Example prompts

  • "Check this webpage [URL] for operable target size issues."
  • "Analyze the interactive elements of [URL] and report any WCAG 2.5.5 violations."
  • "Can you audit [URL] to ensure all buttons meet accessibility guidelines regarding target size?"

Tips & gotchas

This skill requires a URL to analyze. It focuses solely on target size; other accessibility considerations are not assessed.