Sample audit findings.

Turn an observation into a task

A useful finding tells a team where an issue appears, why it matters, and what to change. These examples demonstrate that structure using interface inconsistencies and accessibility concerns you can inspect alongside the report.

The screens are demonstration specimens. They illustrate the format and reasoning of a review; they are not findings about your product.

Prioritize by impact

An issue that prevents someone from completing a task deserves attention before a small visual inconsistency. Read the proposed severity alongside the affected behavior, then consider the context: how often the pattern appears, who encounters it, and whether a workaround exists.

A fix may belong in a shared component, a token, documentation, or the product itself. Identify that owner before putting the finding into a backlog. A report is useful when the next person can act on it.

Establish your own starting point

The design system scorecard offers a broader self-assessment across components, accessibility, tokens, documentation, and handoff. Use it to identify questions worth investigating, then verify those questions in the interfaces your team maintains.