The UX audit checklist for 2026, with the source behind every item

A UX audit checks a site or app against usability heuristics, accessibility standards, performance thresholds and real user data, then ranks the problems by severity. Use three to five independent evaluators, test against WCAG 2.2 AA and Core Web Vitals at the 75th percentile, and turn findings into a prioritised backlog.

Most UX audit checklists online are lists of good intentions: "check navigation", "make it accessible", "test on mobile". They rarely name a standard, an evaluator count or a threshold, so two teams using the same list get different results. This checklist links every line to the source behind it: Nielsen Norman Group for heuristics and severity, W3C for accessibility, web.dev for performance and Baymard for checkout. Legal dates were checked on 23 October 2026. Accessibility law is summarised here as context, not legal advice.

What should you prepare before a UX audit?

An audit without goals produces a long list of opinions. Set these up first:

1. Business goals and success metrics. What should the product do better: sign-ups, completed checkouts, fewer support tickets, faster task completion?
2. Key user journeys. Pick three to six journeys that matter most, such as "find a product and buy it" or "invite a teammate". The audit walks these, not every page.
3. Users and contexts. Who uses the product, on which devices, and in what conditions? A field app used on a phone in sunlight needs different checks from a desktop dashboard.
4. Analytics and field data access. Analytics funnels, search terms, error logs, support tickets and Core Web Vitals field data (from the Chrome UX Report or your own monitoring).
5. Scope and standards. Agree in writing which pages, platforms and standards are in scope (for example, WCAG 2.2 AA and Core Web Vitals) and who receives the findings.
6. A severity scale. Agree how findings will be rated before anyone starts, so priorities are not argued afterwards.

How do you run a heuristic evaluation with Nielsen's 10 heuristics?

Heuristic evaluation is the core of most UX audits. Jakob Nielsen developed the heuristics "in collaboration with Rolf Molich in 1990", and NN/g still publishes them as the standard set:

How many evaluators? NN/g's guide to conducting a heuristic evaluation says "three to five people should independently evaluate" the design. The reason is in Nielsen's original research: "single evaluators found only 35 percent of the usability problems". Different people spot different problems, and pooling them gives far better coverage.

The process, step by step:

1. Brief evaluators on users, goals and the journeys in scope.
2. Each evaluator works alone, walking each journey at least twice: once to learn the flow, once to inspect each screen against the heuristics.
3. Each records every problem with the screen, the heuristic it breaks, evidence (a screenshot) and a suggested fix.
4. Merge findings into one list and remove duplicates.
5. Rate each problem for severity, ideally independently, then agree a final rating.

The severity scale. NN/g's severity ratings combine three factors: frequency, impact and persistence. The scale runs from 0 to 4:

Which accessibility checks belong in a UX audit (WCAG 2.2 AA)?

Accessibility is part of usability, so a UX audit should include it. Use WCAG 2.2 at level AA as the target. W3C's What's new in WCAG 2.2 says it became a W3C Recommendation on 5 October 2023 (the current edition of WCAG 2.2 is dated 12 December 2024), and on 21 October 2025 W3C announced that WCAG 2.2 "is now an approved International Organization for Standardization (ISO) standard: ISO/IEC 40500:2025" (W3C news).

WCAG 2.2 adds nine success criteria:

W3C also notes that "4.1.1 Parsing is obsolete and removed from WCAG 2.2", so don't spend audit time on HTML validation for that criterion.

Beyond the new criteria, check the basics that still fail most often: text and non-text contrast, alt text, form labels and error messages, heading structure, keyboard access to everything, visible focus, captions for video, zoom and reflow to 320 CSS pixels, and screen reader announcements for dynamic content. Combine automated tools (which catch only part of the problems) with manual keyboard and screen reader testing. For a full conformance audit, see website accessibility.

Which performance checks matter (Core Web Vitals)?

Slow or jumpy pages are a usability problem. Use Google's Web Vitals thresholds, measured at the 75th percentile of real page loads, split by mobile and desktop:

Checks to include:

• Use field data first (Chrome UX Report or real user monitoring), then lab tools to diagnose causes.
• Check the key journeys, not just the home page. Product, search and checkout pages often perform worst.
• Look for the usual causes: oversized hero images, render-blocking scripts, third-party tags, web fonts, heavy JavaScript on interaction, and images or ads without reserved space.
• Retest on a mid-range Android phone on a mobile connection, not only on a fast laptop.

What should you check in forms and checkout?

Forms are where users give up. Baymard's checkout usability research puts the average documented cart abandonment rate at 70.19% on its research page; its cart abandonment list gives 70.22% as of 22 September 2025, averaged across 50 studies. Not all of that is fixable, but much of the friction is.

Checks to include:

• Field count: remove every field you don't need. Combine name fields where possible.
• Labels and errors: visible labels (not placeholder-only), inline validation after the user leaves a field, and error messages that say how to fix the problem.
• Input types: the right mobile keyboard for email, phone and numbers; autocomplete attributes for addresses and cards.
• Guest checkout: don't force account creation before purchase.
• Costs up front: shipping, taxes and fees visible before the final step.
• Redundant entry: "billing same as shipping" by default (WCAG 3.3.7).
• Authentication: allow paste and password managers; offer passwordless or email codes where suitable (WCAG 3.3.8).
• Trust and help: clear returns information, security cues near payment, and help in the same place on every step (WCAG 3.2.6).

How do you audit content, navigation and information architecture?

• Labels: navigation uses the words users use, confirmed with search logs and support tickets, not internal jargon.
• Findability: key tasks are reachable from the home page and from search; check zero-result searches.
• Hierarchy: one clear H1 per page, logical headings, and the most important content first.
• Wayfinding: breadcrumbs or clear section markers on deep pages; the current location is always visible.
• Readability: short sentences, plain language, scannable lists, and link text that makes sense out of context.
• Consistency: the same component and the same words for the same action everywhere.
• Empty, loading and error states: every list, search and dashboard has a helpful message when there is nothing to show or something fails.

Which legal dates should a UX audit flag?

A UX audit is not a legal review, but it should flag accessibility deadlines that affect the product. These are the dates as published on official sites, checked on 23 October 2026:

WCAG 2.2 builds on 2.1, so an audit to 2.2 AA also covers the 2.1 AA criteria, apart from 4.1.1 Parsing, which 2.2 removed. Ask your legal adviser which obligations apply to you; an audit tells you where the product stands, not whether you are legally compliant.

What does the full UX audit checklist look like?

Severities are starting points. Adjust them using NN/g's frequency, impact and persistence factors for your product.

UX audit vs usability testing: what's the difference?

They work best together. Run the audit first to fix obvious problems cheaply, then test the riskiest journeys with users. If the audit uncovers conversion problems, a CRO programme can test the fixes with real traffic.

How can Elgrith help?

Elgrith has delivered 1,000+ projects for 250+ clients since 2015, from our New Delhi headquarters and client centers in New York, London and Shanghai. Our UX audit team runs heuristic evaluations with multiple independent evaluators, WCAG 2.2 checks and Core Web Vitals reviews, and gives you a severity-ranked backlog. For full accessibility conformance work, see website accessibility; to fix what the audit finds, our UI/UX design team takes it from there. Accessibility findings are audit and remediation guidance, not legal advice. You get a fixed written quote after a free call. Book a call or start a project.