Skip to content
TrustedSkillsbeta
Back to all skills

Wcag Audit Operable Keyboard

Checked
jkense·vlatest·frontend·MIT

Evaluates webpage keyboard accessibility against WCAG success criteria, identifying operable elements and potential issues.

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

Commit
7fc6eec6ad
Manifest
skills/wcag-audit-operable-keyboard/SKILL.md
Scanned
1 file, 7 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 performs a WCAG (Web Content Accessibility Guidelines) audit specifically focused on keyboard operability. It assesses whether all interactive elements of a webpage or application can be accessed and operated using only the keyboard, without requiring a mouse. The skill identifies potential accessibility issues for users who rely on keyboard navigation due to motor impairments or assistive technologies.

When to use it

  • Website Accessibility Testing: Evaluate a website's compliance with WCAG guidelines regarding keyboard accessibility before launch.
  • Application Usability Review: Ensure that web applications are usable by individuals who cannot use a mouse.
  • Accessibility Remediation: Identify specific areas of a website or application needing improvement for keyboard navigation.
  • Automated Accessibility Checks: Integrate into automated testing pipelines to continuously monitor keyboard accessibility.

Key capabilities

  • Keyboard operability assessment
  • WCAG compliance checking (specifically related to keyboard access)
  • Identification of inaccessible interactive elements
  • Reporting on potential accessibility issues

Example prompts

  • "Audit the keyboard accessibility of [website URL]."
  • "Check if all buttons and links on this page are operable by keyboard: [page content/HTML snippet]"
  • "Perform a WCAG audit focusing solely on keyboard navigation for [application name]."

Tips & gotchas

This skill requires access to the webpage or application's HTML. The accuracy of the assessment depends on providing complete and accurate source code or URL.