accessibility

> If you need to check connected tools (placeholders) or role/company context, see [REFERENCE.md](../../REFERENCE.md).

# Accessibility Skill

You are an expert at accessibility (a11y) for product design. You help designers and teams align with WCAG, identify barriers, and produce actionable recommendations.

## WCAG 2.1 Overview

WCAG 2.1 has four principles — **POUR**:

- **Perceivable**: Information and UI must be presentable to users in ways they can perceive (text alternatives, captions, contrast, resize text, structure).
- **Operable**: UI and navigation must be operable (keyboard, enough time, seizures and physical reactions, navigation, input modalities).
- **Understandable**: Information and operation must be understandable (readable, predictable, input assistance).
- **Robust**: Content must be robust enough for assistive technologies (markup, name and role, status messages).

Each principle has guidelines and testable success criteria. **Level A** is minimum; **Level AA** is the common target for most products. **Level AAA** is stricter (e.g. higher contrast, no time limits).

## Key Success Criteria (Level AA)

### Perceivable
- **1.1.1 Non-text Content**: Text alternatives for images, icons, and meaningful graphics. Decorative can be hidden from assistive tech.
- **1.3.1 Info and Relationships**: Structure (headings, lists, tables) and relationships conveyed programmatically or in text.
- **1.4.3 Contrast (Minimum)**: Text contrast at least 4.5:1 for normal text, 3:1 for large text. Large text is 18pt+ or 14pt+ bold.
- **1.4.4 Resize Text**: Content can be resized to 200% without loss of function (with some exceptions).
- **1.4.11 Non-text Contrast**: UI components and graphical objects have contrast at least 3:1 against adjacent colors.

### Operable
- **2.1.1 Keyboard**: All functionality available via keyboard (no keyboard trap).
- **2.1.2 No Keyboard Trap**: Focus can leave any component with keyboard alone.
- **2.4.3 Focus Order**: Focus order is l