| name | accessibility-audit |
| description | WCAG 2.1 AA accessibility audit skill for Angular 21.x and Flutter 3.41.x. Use when auditing UI for accessibility compliance, identifying barriers, establishing automated testing, or preparing compliance evidence. Covers axe-core automated scanning, keyboard navigation, screen reader compatibility, color contrast, cognitive accessibility, and CI/CD integration. |
| allowed-tools | Read, Grep, Glob, Bash |
| agent | accessibility-auditor |
| context | fork |
| metadata | {"triggers":"accessibility audit, WCAG, a11y, screen reader, keyboard navigation, color contrast, focus management, ARIA, Semantics widget, axe, pa11y, inclusive design, accessibility compliance","related-skills":"angular-spa, flutter-mobile, ui-standards-tokens, design-system, browser-testing","domain":"quality","role":"specialist","scope":"review","output-format":"report","source":"adapted from community (antigravity-awesome-skills)"} |
| last-reviewed | 2026-03-14 |
Accessibility Audit
Iron Law: Before auditing any component, READ the actual file first.
Do not flag violations based on memory — verify at file:line and show evidence.
WCAG 2.1 AA compliance audit for Angular 21.x and Flutter 3.41.x. Use to audit UI components, establish automated testing, identify accessibility barriers, and prepare compliance evidence.
When to Use
- Auditing Angular or Flutter UI for WCAG 2.1 AA compliance
- Adding automated accessibility tests to CI/CD
- Identifying and remediating accessibility barriers
- Preparing compliance evidence for stakeholders
- Reviewing a PR that adds UI components
Do Not Use
- For general UI design review without accessibility scope
- For backend services with no UI (Java, NestJS, Python, FastAPI)
- When you cannot access the UI files or artifacts
Process
- Confirm scope — which components, pages, or user journeys to audit
- Run automated scan — axe-core (Angular) or flutter_test semantics (Flutter) for baseline violations
- Perform manual checks — keyboard, screen reader, focus order, contrast
- Map findings to WCAG criteria — severity (Critical / Important / Suggestion) and WCAG criterion
- Provide remediation — exact code fixes with file:line evidence
- Re-test after fixes — confirm each finding is resolved
Reference Files
| File | Contents | Load When |
|---|
reference/angular-a11y-automated.md | axe-core Angular integration, keyboard trap detection, heading structure validation, pa11y | Adding automated a11y tests to Angular project |
reference/flutter-a11y-automated.md | flutter_test semantics testing, SemanticsController patterns, widget test accessibility | Adding automated a11y tests to Flutter project |
reference/manual-testing-checklist.md | Keyboard, screen reader, visual, cognitive manual checklists for both stacks | Running manual audit session |
reference/cicd-integration.md | GitHub Actions workflows for Angular (axe + pa11y) and Flutter (semantic tests) |
