UX Audit Checklist: What to Review and How to Prioritize

A useful UX audit turns an observed problem into a decision your team can make. Start with one important journey, inspect the experience, and record what you know separately from what you suspect.

This checklist follows the UX Signal Studio framework. Use it for a website inquiry flow, an app’s first-use experience, or a complex product task. Adapt the questions to the audience and context.

1. Define the task and the evidence

Write down who is trying to do what, on which device, and what successful completion means. For a service website, that might be choosing a suitable package and submitting an inquiry. For a SaaS product, it might be creating and sharing the first useful output.

• Choose a start and end point so the scope is clear.
• List the pages, roles, and important states involved.
• Gather analytics, support themes, and recordings where available and appropriate.
• Mark missing evidence. An expert review is not the same as observing users.

2. Review the seven layers

• Reality: What evidence says the underlying need exists? Interface inspection alone cannot answer this.
• Clarity: Can someone explain the value, predict the next step, and understand important terms?
• Trust: Are costs, permissions, commitments, and routes to support visible before the decision?
• Utility: Can the experience produce the outcome it promises? Where does the user still need a workaround?
• Usability: Check navigation, keyboard access, focus visibility, form labels, errors, loading states, and mobile layouts. Include task testing where it is in scope.
• Retention signals: If the need repeats, can people resume useful work? For one-time tasks, prioritize successful completion rather than unnecessary return visits.
• Aesthetics: Does hierarchy guide attention? Are text, spacing, contrast, and controls consistent enough to support understanding?

3. Write findings your team can act on

Use this structure for every finding: affected task → observation → evidence → possible consequence → recommendation → validation method. Add an owner and effort estimate with your delivery team.

Hypothetical example: A contact form clears every field after one validation error. The observed behavior is data loss. The likely consequence is repeated effort; abandonment remains a hypothesis until measured. Preserve valid entries, explain the specific error, and test recovery on mobile and with a keyboard.

4. Prioritize without pretending every finding is proven

Consider impact, reach, confidence, and implementation effort. A blocker on an essential task usually deserves attention ahead of a minor visual inconsistency. A high-impact hypothesis with little evidence may need a short test before engineering work.

5. Close the loop

Record a baseline, ship a defined change, and check the same task again. Depending on the goal, monitor task completion, errors, time to value, support requests, or qualified inquiries. Report what changed without assuming the design caused every movement in the metrics.

For a focused review, compare the Website UX Audit and Product UX Audit. If you need to watch people use the experience, explore a UX Testing Sprint. An accessibility review within a UX audit is not a compliance certification.