accessibility-engineering

作者: addyosmani

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.

npx skills add https://github.com/addyosmani/agent-skills --skill accessibility-engineering

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

RationalizationReality
"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)

來自 addyosmani 的更多技能

accessibility
addyosmani
根據 WCAG 2.2 指南審核並改善網頁無障礙性。當被要求「改善無障礙性」、「無障礙審核」、「WCAG 合規」、「螢幕閱讀器支援」、「鍵盤導航」或「使其無障礙」時使用。
developmenttestingcode-review
api-and-interface-design
addyosmani
引導穩定的 API 與介面設計。適用於設計 API、模組邊界或任何公開介面時。適用於建立 REST 或 GraphQL 端點、定義模組間的型別合約,或劃分前後端邊界時。
apidevelopment
best-practices
addyosmani
應用現代網頁開發的最佳實踐,以確保安全性、相容性與程式碼品質。當被要求「套用最佳實踐」、「進行安全稽核」、「現代化程式碼」、「程式碼品質審查」或「檢查漏洞」時使用。
developmentcode-reviewsecurity
browser-testing-with-devtools
addyosmani
透過 Chrome DevTools MCP 在真實瀏覽器中進行測試。適用於建置或除錯任何在瀏覽器中執行的內容。當需要檢查 DOM、擷取主控台錯誤、分析網路請求、分析效能,或使用真實執行期資料驗證視覺輸出時使用。需設定 chrome-devtools MCP 伺服器。
testingdevelopmentbrowser-automation
ci-cd-and-automation
addyosmani
自動化 CI/CD 管線設定。適用於設定或修改建置與部署管線時。當需要自動化品質關卡、在 CI 中配置測試執行器,或建立部署策略時使用。
devopstestingdevelopment
code-review-and-quality
addyosmani
執行多維度程式碼審查。在合併任何變更前使用。在審查自己、其他代理或人類撰寫的程式碼時使用。當需要在程式碼進入主分支前從多個面向評估程式碼品質時使用。
developmentcode-review
code-simplification
addyosmani
簡化程式碼以提升清晰度。適用於重構程式碼以增進可讀性但不改變行為時。適用於程式碼雖可運作但難以閱讀、維護或擴展時。適用於審查已累積不必要複雜性的程式碼時。
developmentcode-review
constraint-driven-development
addyosmani
Establishes a project's quality bar as a written contract and stops agents quietly lowering it. Interviews the user on which dimensions matter, supplies sane default thresholds when they have no number in mind, records everything in CONSTRAINTS.md, and watches the diff for a weakened bar — new @ts-ignore or eslint-disable suppressions, skipped or deleted tests, assertions stripped out, unimplemented stubs, thresholds edited down. Use when no quality bar is written down, when the user says...
developmenttestingcode-review