typography-auditlisted

# Typography audit A repeatable, evidence-producing pass. An audit finds **defects against criteria**. It does not express preferences — that's `typography-critique`. ## 1. When to invoke - "Audit our typography" / "check this page." - Pre-launch or pre-handoff review. - Design-system compliance checking. - Inherited code or design of unknown quality. - Verifying a fix actually landed. ## 2. Required context - **Scope** — which pages, components, breakpoints, locales, themes. - **Criteria** — the design system, brand guidelines, and conformance target. Without stated criteria you're doing critique, not audit. - **Access to the rendered artifact.** An audit from source alone is not an audit. - Which findings are **blocking** vs. advisory. ## 3. Invariant principles - **Audit the rendered result.** CSS review finds a subset of defects and invents others. - **Every finding needs evidence** — the location, the observed value, the expected value, the criterion. "Line-height feels tight" is critique; "body line-height is 1.2, system token is 1.5, at `/pricing`" is a finding. - **Criteria before findings.** Define what pass means before looking, or you'll grade against a standard set after seeing the output. - **Report what you did not check.** An audit that hides its coverage gaps is worse than no audit, because it licenses false confidence. - **Accessibility findings are blocking by default.** They sit at the top of the source hierarchy. - **Passing one criter