---
author: 'Leonardo Uno'
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.'
extras:
  'Add a test matrix for keyboard, screen reader announcement, error
  association, and contrast evidence.'
focus: 'Build and review Angular UIs against WCAG 2.2 AA.'
id: 'angular-accessibility'
improve:
  - 'Use this as the canonical copy and remove the root duplicate.'
  - 'Move long component examples into a reference so the active instructions
    stay task-focused.'
  - 'Add testing commands only when the repository declares axe, Lighthouse, or
    Angular test support.'
name: 'angular-accessibility'
path: '../submitted-skills/Leonardo%20Uno/skills/angular-accessibility/SKILL.md'
status: 'Needs consolidation'
title: 'Angular accessibility'
wins:
  - 'The most complete submitted accessibility guidance.'
  - 'Clear examples for native controls and labels.'
---

# 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.
