interaction-patternslisted

# Interaction Patterns ## Purpose Walk a UI surface (a page, a component, or an end-to-end flow) against Nielsen's 10 usability heuristics and a WCAG 2.2 first-pass for the fast-to-check criteria — keyboard reachability, focus visibility, color contrast, and motion/animation. Produces a finding-by-finding report with severity and a remediation hint. Not a full a11y scan (see `a11y-scan` for tool-driven scanning); this is the structured-thinking pass that catches what tools miss. ## Scope In: - One target surface — page URL, component path, or flow description. - Nielsen's 10 heuristics, applied as a checklist. - WCAG 2.2 fast-check criteria: 2.1.1 (keyboard), 2.4.7 (focus visible), 1.4.3 / 1.4.11 (contrast), 2.3.3 (animation from interactions), 2.2.2 (pause / stop / hide). - A markdown report with severity tags and remediation hints. Out: - Tool-driven a11y scanning (axe, Pa11y, Lighthouse) — that's `a11y-scan`. - Visual design critique (color palette, spacing system, brand cohesion) — that's `mockup-review`. - User research findings against real users — that's `usability-review` with a recruited cohort. ## When to use - Before a feature ships, as a structured second-pass after design hand-off and before QA. - When a designer says "I think this flow is fine" and you want a reproducible heuristic walk to confirm. - For component-library primitives — every primitive should pass the full Nielsen + WCAG fast-check before adoption. - During a design-system u