---
name: angular-accessibility
description: Build and review Angular interfaces for accessible semantics, keyboard use, focus behavior, and clear status feedback. Use when changing Angular templates, forms, dialogs, navigation, or custom controls.
---

# angular-accessibility

## Workflow
1. Inspect the changed interaction and choose native semantic elements first.
2. Check keyboard operation, focus order, visible focus, labels, errors, and dynamic announcements.
3. Use Angular CDK or Material primitives when they provide the expected behavior.
4. Run available accessibility checks and manually test the changed interaction by keyboard.

## Rules
- ARIA supplements native semantics; it does not replace them.
- Do not claim WCAG conformance from one review.
- Read `references/patterns.md` only for dialogs, tables, or custom composite controls.

## Output
Return changed issues, evidence, and any remaining manual checks.
