---
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:
  'Keep one canonical package under `skills/angular-accessibility/` and add an
  eval for a keyboard-only dialog.'
focus: 'Build and review Angular UIs against WCAG 2.2 AA.'
id: 'angular-accessibility-root'
improve:
  - 'This is a duplicate of the nested package; retain only one canonical
    location to avoid drift.'
  - 'Make “WCAG 2.2 AA” an audit target, not a claim of guaranteed compliance.'
  - 'Add a small test matrix and route detailed component patterns to
    references.'
name: 'angular-accessibility'
path: '../submitted-skills/Leonardo%20Uno/SKILL.md'
status: 'Duplicate package'
title: 'Angular accessibility (root copy)'
wins:
  - 'Prioritizes native semantics before ARIA.'
  - 'Covers interaction, focus, forms, and live updates.'
---

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