accessibility-engineering

Prüft bestehende Benutzeroberflächen auf Konformität mit WCAG 2.2 AA und behebt die gefundenen Verstöße. Verwenden Sie diese Funktion, wenn Sie eine Seite oder Komponente auf Barrierefreiheit prüfen, axe-core oder pa11y ausführen, a11y-Verstöße priorisieren oder vor der Veröffentlichung Probleme mit Screenreadern und Kontrasten überprüfen.

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)

Mehr Skills von addyosmani

accessibility
addyosmani
Überprüfen und verbessern Sie die Barrierefreiheit im Web gemäß den WCAG 2.2-Richtlinien. Verwenden Sie dies, wenn Sie aufgefordert werden, "Barrierefreiheit verbessern", "a11y-Audit", "WCAG-Konformität", "Screenreader-Unterstützung", "Tastaturnavigation" oder "zugänglich machen".
developmenttestingcode-review
api-and-interface-design
addyosmani
Leitet zu stabilem API- und Interface-Design an. Verwenden beim Entwerfen von APIs, Modulgrenzen oder öffentlichen Schnittstellen. Verwenden beim Erstellen von REST- oder GraphQL-Endpunkten, beim Definieren von Typverträgen zwischen Modulen oder beim Festlegen von Grenzen zwischen Frontend und Backend.
apidevelopment
best-practices
addyosmani
Wenden Sie moderne Best Practices der Webentwicklung für Sicherheit, Kompatibilität und Codequalität an. Verwenden Sie, wenn Sie aufgefordert werden, "Best Practices anzuwenden", "Sicherheitsaudit durchzuführen", "Code zu modernisieren", "Codequalität zu überprüfen" oder "nach Schwachstellen zu suchen".
developmentcode-reviewsecurity
browser-testing-with-devtools
addyosmani
Testet in echten Browsern über Chrome DevTools MCP. Verwende dies beim Erstellen oder Debuggen von allem, was in einem Browser läuft. Verwende dies, wenn du das DOM inspizieren, Konsolenfehler erfassen, Netzwerkanfragen analysieren, die Leistung profilieren oder die visuelle Ausgabe mit echten Laufzeitdaten überprüfen musst. Erfordert, dass der chrome-devtools MCP-Server konfiguriert ist.
testingdevelopmentbrowser-automation
ci-cd-and-automation
addyosmani
Automatisiert die Einrichtung von CI/CD-Pipelines. Verwenden Sie dies beim Einrichten oder Ändern von Build- und Deployment-Pipelines. Verwenden Sie dies, wenn Sie Qualitätsgates automatisieren, Testrunner in CI konfigurieren oder Bereitstellungsstrategien festlegen müssen.
devopstestingdevelopment
code-review-and-quality
addyosmani
Führt eine mehrdimensionale Code-Überprüfung durch. Vor dem Zusammenführen von Änderungen verwenden. Verwenden, wenn Code überprüft wird, der von Ihnen selbst, einem anderen Agenten oder einem Menschen geschrieben wurde. Verwenden, wenn die Codequalität vor der Integration in den Hauptzweig in mehreren Dimensionen bewertet werden muss.
developmentcode-review
code-simplification
addyosmani
Vereinfacht Code für mehr Klarheit. Verwenden Sie dies beim Refactoring von Code zur Verbesserung der Lesbarkeit, ohne das Verhalten zu ändern. Verwenden Sie dies, wenn Code funktioniert, aber schwerer zu lesen, zu warten oder zu erweitern ist als nötig. Verwenden Sie dies bei der Überprüfung von Code, der unnötige Komplexität angesammelt hat.
developmentcode-review
constraint-driven-development
addyosmani
Legt den Qualitätsmaßstab eines Projekts als schriftlichen Vertrag fest und verhindert, dass Agents ihn unbemerkt senken. Fragt den Nutzer, welche Dimensionen wichtig sind, schlägt sinnvolle Standardgrenzwerte vor, wenn keine konkreten Zahlen vorliegen, hält alles in CONSTRAINTS.md fest und überwacht den Diff auf eine Aufweichung des Maßstabs – neue @ts-ignore- oder eslint-disable-Unterdrückungen, übersprungene oder gelöschte Tests, entfernte Assertions, nicht implementierte Stubs, herabgesetzte Grenzwerte. Verwenden, wenn kein Qualitätsmaßstab schriftlich festgehalten ist oder der Nutzer sagt ...
developmenttestingcode-review