Skillquality 0.45

a11y-audit

Run a WCAG accessibility audit on a web page — checks heading hierarchy, landmark regions, color contrast, ARIA attributes, keyboard navigation, and screen reader compatibility. Use when the user wants to check, test, or audit accessibility (a11y) on a URL or the current page.

Price
free
Protocol
skill
Verified
no

What it does

Use the browser (via the Chrome/Playwright MCP) to audit the page for accessibility issues. Follow the steps below in order.

1. Navigate and baseline

  1. Navigate to the page with navigate_page
  2. Run list_console_messages with types: ["issue"] and includePreservedMessages: true to catch native Chrome accessibility issues (missing labels, invalid ARIA, low contrast)

2. Structure and semantics

  1. Run take_snapshot to capture the accessibility tree
  2. Check heading hierarchy (h1 > h2 > h3, no skipped levels)
  3. Verify landmark regions are present (main, nav, header, footer)
  4. Check page <title> is present and free of typos
  5. Compare snapshot order against a take_screenshot to confirm DOM order matches visual reading order

3. Labels, images, and forms

Using the snapshot:

  • Buttons and links must have an accessible name (not empty)
  • Images must have meaningful alt text, decorative images use alt=""
  • Form inputs must have associated labels — verify with evaluate_script:
    [...document.querySelectorAll('input, select, textarea')]
      .filter(el => !el.labels?.length && !el.getAttribute('aria-label') && !el.getAttribute('aria-labelledby'))
      .map(el => el.outerHTML)
    

4. Keyboard navigation

  1. Press Tab and take a snapshot — locate the focused element in the tree
  2. Continue tabbing through key interactive elements to verify logical focus order
  3. If a modal or dialog is present, verify focus is trapped inside it
  4. Take a take_screenshot to confirm focus indicator is visible

5. Color contrast

Check list_console_messages output for "Low Contrast" issues first. If the environment does not report them, use evaluate_script to check a specific element manually:

const el = document.querySelector('SELECTOR');
const style = getComputedStyle(el);
[style.color, style.backgroundColor]

6. ARIA

Using the snapshot, verify:

  • No ARIA roles that duplicate native semantics (e.g., <button role="button">)
  • No aria-label on elements that already have visible text
  • No invalid role values or misuse of aria-hidden on focusable elements

Report

Group findings by severity:

  • Critical — blocks access entirely
  • Serious — significantly impairs access
  • Moderate — causes confusion or extra effort
  • Minor — small improvements, including typos in visible or <title> text

For each issue: element or selector, what is wrong, and the fix.

When the audit is complete, close the page with close_page.

Capabilities

skillsource-grimlinkskill-a11y-audittopic-agent-skillstopic-ai-toolstopic-bashtopic-dotfilestopic-gittopic-homebrewtopic-laravel-valettopic-macostopic-magento2topic-nodejstopic-phptopic-terminal

Install

Installnpx skills add GrimLink/dotfiles
Transportskills-sh
Protocolskill

Quality

0.45/ 1.00

deterministic score 0.45 from registry signals: · indexed on github topic:agent-skills · 8 github stars · SKILL.md body (2,522 chars)

Provenance

Indexed fromgithub
Enriched2026-05-18 19:08:54Z · deterministic:skill-github:v1 · v1
First seen2026-05-18
Last seen2026-05-18

Agent access