impeccable-audit

MANDATORY PREPARATION

Invoke /impeccable-design — it contains design principles, anti-patterns, and the Context Gathering Protocol. Follow the protocol before proceeding — if no design context exists yet, ask the user directly for target audience, use cases, and brand personality first.

Run systematic technical quality checks and generate a comprehensive report. Don't fix issues — document them for other commands to address.

This is a code-level audit, not a design critique. Check what's measurable and verifiable in the implementation.

Diagnostic Scan

Run comprehensive checks across 5 dimensions. Score each dimension 0-4 using the criteria below.

1. Accessibility (A11y)

Check for: Contrast issues (text <4.5:1), missing ARIA labels/roles, keyboard navigation gaps, illogical tab order, semantic HTML issues, missing alt text, forms without labels.

Score 0-4: 0=Inaccessible (fails WCAG A), 1=Major gaps, 2=Partial (some a11y, significant gaps), 3=Good (WCAG AA mostly met), 4=Excellent (WCAG AA fully met)