Science of Apps - Launchpad · Checklist

The UX audit checklist,
a free template

A UX audit checklist should follow the user's journey: first impression (findability, landing page, pricing, speed), joining (sign-up, onboarding), the core task, payment, retention and accessibility on every screen. Check each item against Nielsen's 10 usability heuristics and WCAG 2.2, record evidence for every failure, and rate its severity so you fix the worst first.

By , FounderUpdated 8 min read

Share

Quick answer: What should a UX audit checklist include?

  1. Arrive: findable, clear landing page, visible pricing, trust signals, fast and stable.
  2. Join: short sign-up, recovery that works, onboarding to one real result.
  3. Use: the core task end to end, navigation, microcopy, empty, loading and error states.
  4. Pay: a clear paywall, honest upgrade, checkout that works on mobile.
  5. Stay and every screen: notifications, settings, help; WCAG 2.2 accessibility and visual consistency.

Key takeaways

  • Audit the journey in the order users take it; most problems hide in hand-offs between screens.
  • Use Nielsen's 10 heuristics as the 'why' for usability findings and WCAG 2.2 for accessibility.
  • Record evidence for every failed item: a screenshot, a measurement or a recording.
  • Rate severity, then fix the few critical items first; a long unordered list rarely gets fixed.
  • Re-check after fixing; an audit is a loop, not a one-off document.

A UX audit is only as good as its checklist, and most checklists online are lists of screens. Users don't experience screens; they experience a journey, and most problems hide where one step hands off to the next. This free template follows that journey, from the search result to settings, with each check tied to a principle you can cite: one of Nielsen's 10 usability heuristics, a WCAG 2.2 accessibility requirement or a behavioural law. Copy it, walk your product as a new user on desktop and mobile, and record evidence for every failure. Jump to how to use it, the checklist or how to score findings.

Journey stages
6
Checks in this template
60
Nielsen heuristics behind the usability checks
10
WCAG version behind the accessibility checks
2.2

How to use this checklist

Diagram of 5 steps for how to use this checklist: 1. Choose one journey; 2. Use fresh eyes; 3. Tick or fail every item; 4. Tag the principle; 5. Rate severity.
How to use this checklist
  1. Choose one journey. Start with the one that makes you money: usually sign-up to first result, or browse to checkout.
  2. Use fresh eyes. A clean browser, a new account, on desktop and on a mid-range phone.
  3. Tick or fail every item. For each failure, save evidence: a screenshot, a recording or a measurement.
  4. Tag the principle. Note the heuristic (H1–H10), WCAG criterion or law it breaks.
  5. Rate severity. Use the scale at the end, then fix critical items first.

1. Arrive: first impression

Checklist: 1. Arrive: first impression — Findable; One-line clarity; Primary action obvious; Pricing findable; Trust signals real; Privacy and terms present; Fast; Stable; Works without errors; Mobile layout holds.
1. Arrive: first impression
  • Findable — the product appears when you search its name and its main problem, on Google and in AI assistants
  • One-line clarity — the landing page says what it does and for whom in the first sentence (H2)
  • Primary action obvious — one clear call to action above the fold (Hick's Law)
  • Pricing findable — within one click from the homepage
  • Trust signals real — reviews, logos or badges that link to a source (social proof)
  • Privacy and terms present — and readable
  • Fast — the main content appears quickly on a mid-range phone
  • Stable — nothing jumps as the page loads
  • Works without errors — no console errors, broken images or dead links
  • Mobile layout holds — no horizontal scrolling at 320px wide

2. Join: the first few minutes

Checklist: 2. Join: the first few minutes — Sign-up asks only what's needed; Social or passwordless sign-in; Clear errors; Password rules shown before failure; Account recovery works; Email verification doesn't block value; Onboarding reaches one real result fast; Progress is visible; Users can skip
2. Join: the first few minutes
  • Sign-up asks only what's needed — no phone number or card before value, unless essential
  • Social or passwordless sign-in — where your users expect it
  • Clear errors — inline, specific, and they say how to fix it (H9)
  • Password rules shown before failure — not after (H5)
  • Account recovery works — the reset email arrives and the link works on mobile
  • Email verification doesn't block value — or explains why it must
  • Onboarding reaches one real result fast — the first moment of value
  • Progress is visible — steps and status are shown (H1)
  • Users can skip or go back — without losing work (H3)
  • No empty first screen — examples, templates or sample data instead

3. Use: the everyday job

  • The core task works end to end — on desktop and mobile
  • Navigation matches users' words — labels in their language, not internal names (H2)
  • Consistent patterns — the same action looks and works the same everywhere (H4)
  • Recognition, not recall — options visible, not memorised from another screen (H6)
  • Search works — tolerant of typos, with useful no-result states
  • Empty states guide — say what to do next
  • Loading states reassure — show progress for anything slow (H1)
  • Errors help recovery — plain language, a way forward (H9)
  • Destructive actions are confirmed or undoable — (H3, H5)
  • Shortcuts for frequent users — without confusing new ones (H7)
  • Microcopy is clear — buttons say what happens ("Save draft", not "Submit")
  • Not overloaded — each screen has one main job (cognitive load, H8)

4. Pay: where value turns into revenue

Checklist: 4. Pay: where value turns into revenue — The paywall explains what's included; Plans are few and comparable; Price shown with tax and currency; Trial terms clear; Checkout is short; Payment errors are specific; Works on mobile; Receipts and invoices sent; Downgrade and cancel are possible
4. Pay: where value turns into revenue
  • The paywall explains what's included — and what happens to the user's work
  • Plans are few and comparable — highlight one recommended plan
  • Price shown with tax and currency — no surprises at checkout
  • Trial terms clear — when it ends, what it costs, how to cancel
  • Checkout is short — the fewest possible fields
  • Payment errors are specific — and keep entered details
  • Works on mobile — including wallet payments where expected
  • Receipts and invoices sent — and findable later
  • Downgrade and cancel are possible — and honest
  • No dark patterns — no hidden pre-ticked add-ons or confirm-shaming

5. Stay: what brings people back

Checklist: 5. Stay: what brings people back — Notifications are useful; Settings are findable; Account and profile editable; Data export or deletion available; Help is in context; Support is reachable; What's new is communicated; Re-entry is easy.
5. Stay: what brings people back
  • Notifications are useful — relevant, timely and easy to control
  • Settings are findable — and grouped logically
  • Account and profile editable — including email and password
  • Data export or deletion available — where users expect it
  • Help is in context — at the points people get stuck (H10)
  • Support is reachable — and says how long a reply takes
  • What's new is communicated — without blocking work
  • Re-entry is easy — users can pick up where they left off

6. Every screen: accessibility and consistency

Check these on every screen against WCAG 2.2.

  • Text contrast sufficient — including placeholder and disabled text
  • Keyboard accessible — every action reachable and visibly focused
  • Labels on every input — not just placeholders
  • Images have text alternatives — decorative ones are hidden from screen readers
  • Errors identified in text — not by colour alone
  • Touch targets large enough — and not crowded
  • Headings structured — one H1, logical order
  • Motion respects reduced-motion settings — nothing flashes
  • Zoom to 200% works — without losing content
  • Visual consistency — type, spacing, colour and components match the design system
W3C Web Content Accessibility Guidelines WCAG 2.2 page marked W3C Recommendation, with a table of contents starting with Perceivable
WCAG 2.2, the accessibility standard behind the every-screen checks.Image: W3C · Screenshot shown for commentary, 17 Nov 2026 · source

How to score findings

SeverityMeaningFix
CriticalBlocks users from completing a key taskNow
Needs to be fixedCauses errors or abandonment for many usersThis sprint
Needs improvementSlows or confuses users but they get throughPlan it
RecommendationPolish or an opportunityWhen convenient
GoodWorks well; keep it—

Table: A five-level severity scale for UX audit findings

Order by severity, then by how many users hit the problem. A short list of critical fixes gets done; a 60-item list in no order doesn't.

The heuristics, for tagging

Nielsen Norman Group article 10 Usability Heuristics for User Interface Design by Jakob Nielsen
Nielsen's 10 usability heuristics, the H1–H10 tags in this checklist.Image: Nielsen Norman Group · Screenshot shown for commentary, 17 Nov 2026 · source

H1 Visibility of system status · H2 Match between the system and the real world · H3 User control and freedom · H4 Consistency and standards · H5 Error prevention · H6 Recognition rather than recall · H7 Flexibility and efficiency of use · H8 Aesthetic and minimalist design · H9 Help users recognize, diagnose, and recover from errors · H10 Help and documentation.

Prefer it done for you?

Science of Apps product investigation page with the headline Product intelligence that shows its work
The Science of Apps product investigation: the same journey, tested with evidence.Image: Science of Apps · © Science of Apps · source

List your product free on Science of Apps Launchpad, and once it's live it's tested across the same journey: loaded in a real browser on desktop and mobile, measured automatically and reviewed by experts, with every finding backed by evidence, rated on the five verdicts above and approved by an analyst.

Areas tested
22
Automatic measurements
39
Expert checks behind your login
74
Verdicts that rank what to fix first
5

Ready to audit?

How we built this template

The usability checks map to Nielsen's 10 usability heuristics (Nielsen Norman Group), the accessibility checks to the W3C's WCAG 2.2 Recommendation, and the journey to the stages Science of Apps uses in its product investigations. It's a starting template, not a compliance certification; for legal accessibility conformance, test against the full WCAG success criteria.

Key terms, defined

  • UX audit checklist: a list of checks used to review a product's usability and accessibility consistently.
  • Heuristic (H1–H10): one of Nielsen's 10 usability principles.
  • WCAG 2.2: the W3C's Web Content Accessibility Guidelines, version 2.2.
  • Severity: how badly a problem blocks users, used to order fixes.
  • Dark pattern: an interface trick that pushes users into choices they didn't intend.

Frequently asked questions

What should a UX audit checklist include?

Checks for every stage of the user journey: findability and first impression, sign-up and onboarding, the core task, payment and upgrade, retention features and accessibility on every screen. Each item should map to a principle, such as one of Nielsen's 10 usability heuristics or a WCAG 2.2 criterion, so findings are explainable.

How do I do a UX audit with a checklist?

Pick the journeys that matter most (usually sign-up and the core task), walk them as a new user on desktop and mobile, tick each check, and for every failure save evidence and note a severity. Then sort by severity and fix the critical items first.

What's the difference between a UX audit and a heuristic evaluation?

A heuristic evaluation checks an interface against usability principles such as Nielsen's 10 heuristics. A UX audit is broader: it usually includes a heuristic evaluation plus accessibility checks, performance measurements, analytics and a review of the whole journey.

How long does a checklist-based UX audit take?

For one key journey on one platform, a few hours. For a full product on desktop and mobile, a few days. Start with the journey that makes you money.

Can a UX audit be automated?

Partly. Speed, some accessibility checks and broken links can be measured automatically. Judging clarity, flow and trust needs a person walking the product. The most useful audits combine both, with every finding reviewed before it's acted on.

How do I prioritise UX audit findings?

Rate each by severity (how badly it blocks users) and reach (how many users hit it). Fix critical blockers on high-traffic paths first, then high-reach annoyances, then polish.

Sources

  1. Nielsen Norman Group — 10 usability heuristics for user interface design (Jakob Nielsen, 1994; reviewed 2024)
  2. W3C — Web Content Accessibility Guidelines (WCAG) 2.2, W3C Recommendation
  3. Science of Apps — Product investigation: what we investigate and how
  4. Science of Apps — Launchpad: launch your product free
  5. Checked November 17, 2026. Figures that change — fees, salaries, prices — are reviewed every six months; if something is out of date, tell us.
Pass it on

Know someone who'd enjoy this?

Send it to them — one tap, no sign-up. Good ideas travel best between friends.

Keep exploring

Where to go from here

Join free

Get the ideas, not the noise.

Sign up with Google and we’ll send you short UX psychology tips by email — why people tap, stall and leave, and what to do about it. Unsubscribe anytime. Prefer something to keep? Get the free Laws of UX guide as a PDF.

Get the free Laws of UX PDFFree · no spam · unsubscribe anytime
Free, forever

Launch day ends. Your listing shouldn't.

Prefer it done for you? List your product free and, once it's live, it's tested end to end across 22 areas with 39 automatic measurements and 74 expert checks, with a detailed report.

Free PDF · 74 pages · 2 editions

The Laws of UX, in one field guide

60 research-backed principles in 6 categories — what each one means, why it works on the human brain and how to use it on your own screens. Written by Sushant Singh, founder of Science of Apps, who has scaled consumer apps to lacs of users and spent 10+ years leading product across startups and digital businesses in the US, EU & India.

Pick your edition
Free PDF · 90 pages · 2 editions

100+ Subscription Paywalls, decoded

110 real paywalls from top apps, taken apart, rated out of 5 and decoded with the Laws of UX — plus the frameworks, copy and checklists to ship your own. By Sushant Singh, founder of Science of Apps.

  • 110 paywalls rated
  • 34 Laws of UX
  • 12 frameworks

Which paywall scored 4.8 out of 5, and which scored 2.6? It’s all inside.

Pick your edition
Free PDF · 188 pages · 2 editions

Unmistakable: the logo book

How the world’s greatest logos are made, chosen and kept — and how to make yours. 98 short lessons and 19 true stories for founders, designers and the curious. By Sushant Singh, founder of Science of Apps.

  • 98 lessons
  • 19 true stories
  • 60+ real logos

Why did a $35 sketch become the Swoosh, and why did Gap lose its nerve in six days? It’s all inside.

Pick your edition