Index of every page on this site: llms.txt
All skills
addyosmani avatar

/accessibility-engineering

@8c99fa3
by Addy Osmaniaddyosmani/agent-skills119k stars
12,412
Run it yourself

Audits existing interfaces for WCAG 2.2 AA conformance and remediates the violations found. Use when auditing a page or component for accessibility, running axe-core or pa11y, triaging a11y violations, or checking screen reader and contrast issues before shipping.

Use this Skill: https://skilld.dev/gh/addyosmani/agent-skills/accessibility-engineering

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈73 tokens for metadata: the name and description. ≈1.8k when used: this file.

Description uses 3.6% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈292 characters, or 3.6%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Accessibility Engineering

Overview

Accessibility is not a polish step — it's a legal requirement in many jurisdictions, an engineering quality standard, and a prerequisite for shipping. This skill audits existing interfaces, triages the findings, and remediates verified violations. The goal is WCAG 2.2 AA compliance supported by automated tools and manual testing.

When to Use

  • Before shipping a user-facing change that needs an accessibility audit
  • When a11y issues are reported (e.g., "screen reader can't read this", "keyboard navigation broken")
  • When auditing an existing interface for compliance
  • When triaging axe-core or pa11y findings
  • When remediating verified accessibility violations

Do NOT use for building new UI components from scratch; use frontend-ui-engineering for construction guidance. Do not use for backend-only changes, CLIs, or library code with no UI output.

Workflow

Phase 1: Route New UI Work

For component construction, interaction patterns, and focus-management guidance, use ../frontend-ui-engineering/SKILL.md. Do not restate that skill here. Return to this workflow once an interface exists and needs auditing or remediation.

Phase 2: Run Automated Audit

Execute accessibility checks in this order:

# axe-core rules through pinned @axe-core/cli (the axe-core package ships no CLI)
npx --yes @axe-core/cli@4.13.0 http://localhost:3000 --exit

# Keep the JSON for the accessibility-auditor
npx --yes @axe-core/cli@4.13.0 http://localhost:3000 --dir ./a11y-reports --save axe.json

# Pinned pa11y for HTML validation (WCAG2AA rules via HTML_CodeSniffer)
npx --yes pa11y@9.1.1 http://localhost:3000

For a combined report, run bash skills/accessibility-engineering/scripts/audit-a11y.sh url <url> --json. It runs both pinned tools, records their status and versions, and fails rather than reporting a clean result when either tool does not produce a valid report.

Review the violations grouped by severity:

  • Critical — Blocks screen reader access entirely (missing alt text on info images, empty buttons)
  • Serious — Makes content difficult or impossible to access (low contrast, missing labels)
  • Moderate — Causes confusion or extra effort (heading level skips, redundant ARIA)
  • Minor — Cosmetic or progressive enhancement (missing lang attribute on inner elements)

For each violation, verify it's a real issue (not a false positive) by inspecting the element in the browser.

Phase 3: Manual Testing

Automated checks are a smoke test, not proof of conformance. Complete the audit manually.

Keyboard audit:

  1. Tab through every interactive element — can you see where you are?
  2. Activate buttons and links with Enter/Space
  3. Close modals with Escape
  4. Navigate lists with Arrow keys
  5. Verify no keyboard traps exist

Screen reader audit (VoiceOver on macOS, NVDA on Windows):

  1. Navigate by heading (VoiceOver: Ctrl+Option+Cmd+H) — is the structure logical?
  2. Navigate by landmark (open the rotor with Ctrl+Option+U, choose Landmarks) — are regions labeled?
  3. Navigate by link (open the rotor with Ctrl+Option+U, choose Links) — do link descriptions make sense out of context?
  4. Interact with a form — are labels announced? Are error messages read?
  5. Navigate a dynamic update — are changes announced?

Visual audit:

  1. Verify color contrast (4.5:1 text, 3:1 large text, 3:1 UI components)
  2. Zoom to 200% — does layout break or overlap?
  3. Test with forced colors / high contrast mode (Windows High Contrast)
  4. Reduce motion (prefers-reduced-motion) — are animations disabled?
  5. Test focus visibility — is the focus ring visible against all backgrounds?

Phase 4: Fix Violations

For each finding, apply the remediation in order:

  1. Fix the root cause — Replace a <div> with <button>, add <label>, set alt text
  2. Add ARIA as bridge — If native HTML can't express the pattern, add ARIA attributes
  3. Test the fix — Re-run the automated check and manual verification

Apply the accessibility checklist (../../references/accessibility-checklist.md) as a minimal baseline.

Common Rationalizations

Rationalization Reality
"We'll fix a11y later" Delayed remediation compounds across components and can create legal liability. Audit before shipping.
"Automated tools caught everything" Automated checks cannot prove keyboard or screen reader behavior. Manual testing is mandatory.
"Screen reader users are a tiny minority" Accessibility is a requirement, not a usage-share calculation. Keyboard navigation, captions, and clear structure also help users across contexts.
"This is an internal tool, it doesn't need a11y" Internal tools are subject to the same regulations. Disabled employees and contractors need access.
"I'll just use aria-label everywhere" ARIA is a bridge, not a foundation. Semantic HTML first. Overusing ARIA creates maintenance burden and can make things worse.
"The design system handles accessibility" Design systems provide accessible primitives. How you compose them determines whether the result is accessible.
"The audit passed axe-core, so we're done" Pass axe-core as a smoke test, then test with screen readers and keyboard. A green lighthouse score is not a clean bill of health.

Red Flags

  • Elements that look clickable but aren't keyboard-focusable
  • Color as the sole indicator of state (red for error, green for success)
  • Focus outline removed without a visible replacement
  • Missing labels on form inputs
  • No heading hierarchy or skipped heading levels
  • Empty or unlabeled buttons and links
  • Modals that don't trap focus or restore focus on close
  • No alt text on meaningful images (or alt="" missing on decorative ones)
  • Touch targets that fail SC 2.5.8's 24x24 CSS px size-or-spacing requirement and do not qualify for an exception (AA; 44x44 is the AAA target, SC 2.5.5)
  • Autoplaying video or audio without controls
  • Low contrast text (especially on hover, disabled states, placeholders)

See Also

  • ../../references/accessibility-checklist.md — Quick reference for WCAG 2.2 AA
  • ../frontend-ui-engineering/SKILL.md — Building accessible components from the start
  • ../../agents/accessibility-auditor.md — Dedicated a11y audit persona for deep reviews

Verification

After completing the accessibility workflow:

  • Automated audit passes with no Critical or Serious violations
  • All interactive elements are keyboard accessible (Tab, Enter, Escape, Arrow keys)
  • Screen reader navigation by heading, landmark, and link verified with a named browser + AT pair (or recorded as manual and untested — never reported as verified)
  • Focus order matches visual order
  • Color contrast passes 4.5:1 text / 3:1 large text / 3:1 UI components
  • All form inputs have associated labels
  • All images have appropriate alt text
  • Dynamic content changes are announced (aria-live)
  • Page is usable at 200% zoom with no content loss
  • Touch targets satisfy SC 2.5.8's 24x24 CSS px size-or-spacing requirement or a normative exception (AA); 44x44 is the enhanced AAA target (SC 2.5.5)

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning2d3 checks · Risk SAFE
  • Gen Agent Trust Hub2d

    This skill provides a structured workflow for performing accessibility audits using industry-standard tools like axe-core and pa11y. It includes a bash script to automate the execution of these tools and combine their results into a single report. The skill follows security best practices by pinning dependency versions and uses standard Node.js patterns for data processing. While it processes external web content which creates a surface for indirect prompt injection, this behavior is necessary for its purpose and is managed safely.

  • Socket2d

    No alerts

  • Snyk2d

    Risk: MEDIUM · 1 issue

Signed by skilld at 8c99fa3. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 days ago.

Activeupdated 5 days ago

README badge

README badge for addyosmani/agent-skills/accessibility-engineering