TL;DR

A practical UX checklist covering navigation, WCAG 2.1 AA accessibility, form design, Core Web Vitals performance, touch-first mobile design, and content strategy — use it to audit existing products and set quality baselines.

A practical checklist for modern products

This article is part of our UX design guide. Start there for the big picture.

Best practices aren’t rules — they’re starting points. Every product context is different, and the best designers know when to follow conventions and when to break them on purpose. That said, these practices represent hard-won consensus across the industry. Use this checklist to audit existing products, guide new designs, and set baselines for quality. (Unfamiliar with any of the terms below? Our UX glossary has plain-English definitions.)

Navigation

Good navigation is invisible. Users should always know where they are, where they can go, and how to get back.

  • Keep primary navigation consistent across all pages. Moving it between screens forces users to re-learn the interface.
  • Limit top-level items to seven or fewer. More than that and scanning becomes a chore.
  • Use clear, descriptive labels instead of clever or branded terminology. “Pricing” beats “Investment Options” every time.
  • Provide breadcrumbs for deep hierarchies so users can orient themselves and backtrack quickly.
  • Make the current location obvious — highlighted nav items, active states, breadcrumb trails.
  • Keep critical flows within three clicks from the home page.
  • Include search for content-heavy products. It’s not a replacement for good IA, but it’s a necessary complement.

Accessibility (WCAG 2.1 AA)

Accessibility isn’t optional. It’s a legal requirement in many jurisdictions and the right thing to do everywhere else. And here’s what people often overlook: accessible design improves the experience for all users.

  • Minimum contrast ratio of 4.5:1 for normal text and 3:1 for large text.
  • Text alternatives for all non-decorative images via alt attributes.
  • Full keyboard accessibility — users must be able to navigate, activate, and dismiss every control without a mouse.
  • Semantic HTML (headings, landmarks, lists, form labels) so assistive technologies can parse the page.
  • Visible focus indicators. Never strip the default outline without providing a custom alternative that’s equally clear.
  • Screen reader testing with VoiceOver, NVDA, or JAWS. Automated tools only catch about 30% of accessibility issues.
  • Don’t rely on color alone. Use icons, labels, or patterns alongside color for status and meaning.
  • Captions and transcripts for video and audio content.
  • Text resizing up to 200% without breaking the layout.

I’ve worked on projects where accessibility was treated as a final-sprint checkbox, and the rework cost was always higher than doing it right from the start. Build it in early.

Forms

Forms are where users exchange value with your product. Every unnecessary field, confusing label, or unhelpful error message is friction that costs you conversions.

  • Only ask for what you actually need. Each extra field reduces completion rates.
  • Single-column layout. Multi-column forms increase completion time and error rates.
  • Labels above inputs for the fastest scanning and completion. Placeholder-as-label causes usability problems when it disappears on focus.
  • Inline validation as users move between fields, not only on submission.
  • Specific, actionable error messages. “Invalid input” is useless. “Email address must include an @ symbol” actually helps.
  • Group related fields with clear section headings. Break long forms into logical steps.
  • Appropriate input types — email, phone, number, date — to trigger the right mobile keyboard and enable browser autofill.
  • Pre-fill when possible using known data, defaults, or smart suggestions.
  • Make the primary action button dominant and label it with a verb: “Create Account,” not “Submit.”

Performance (Core Web Vitals)

Speed is a UX feature. Users don’t distinguish between “the product is slow” and “the product is bad.” Performance directly impacts satisfaction, engagement, and conversion. (For a framework on tying these metrics to business ROI, see measuring UX success.)

  • Largest Contentful Paint (LCP) under 2.5 seconds. This measures when the main content becomes visible.
  • Interaction to Next Paint (INP) under 200 milliseconds. This measures responsiveness to user input.
  • Cumulative Layout Shift (CLS) under 0.1. Elements shouldn’t jump around as the page loads.
  • Optimize images with modern formats (WebP, AVIF), responsive sizing, and lazy loading for below-the-fold content.
  • Minimize render-blocking resources. Defer non-critical CSS and JavaScript.
  • Skeleton screens or progress indicators for slow-loading content. An empty screen feels broken; a skeleton feels like progress.
  • Aggressive caching for returning users. Second visits should feel instant.

Mobile (touch-first design)

Mobile isn’t a smaller desktop. It’s a different context with different constraints, inputs, and expectations.

  • Touch targets at minimum 44 by 44 pixels per Apple’s Human Interface Guidelines. Small targets cause mis-taps and frustration.
  • At least 8 pixels of spacing between interactive elements to prevent accidental taps.
  • Primary actions within thumb reach. On modern phones, the bottom third of the screen is the comfort zone.
  • Simplified mobile navigation. Hamburger menus work when paired with a visible bottom tab bar for primary destinations.
  • Design for interruption. Mobile users get distracted constantly. Save state automatically and let them pick up where they left off.
  • No hover-dependent interactions. Touch screens don’t have hover. Anything revealed on hover must be accessible via tap or visible by default.
  • Test on real devices. Emulators miss performance issues, touch nuances, and viewport quirks that only surface on actual hardware.

Content

Content is the interface. Users come to products for information, communication, or task completion — all of which depend on clear, well-structured content.

  • Front-load important information. Users scan, they don’t read. Put the most critical content in headings, first sentences, and bullet points.
  • Plain language. Write at a level appropriate for your audience. Skip the jargon unless your users expect it.
  • Consistent voice across all touchpoints. A playful tone in marketing that turns robotic in the product creates whiplash.
  • Clear hierarchy. Use headings, subheadings, lists, and whitespace to make pages scannable.
  • Descriptive link text. “Learn more about pricing” works. “Click here” doesn’t.
  • Helpful, concise microcopy. Tooltips, placeholders, and helper text should clarify, not clutter.

Applying the checklist

No product will hit every item on day one. Use this as a diagnostic tool — find your weakest areas, prioritize by user impact, and iterate. Pick three items from this list that your product currently fails, fix those first, and then come back for the next three. Progress compounds faster than you’d expect. If you want expert help identifying and fixing UX friction points, explore our User Retention & Conversion Design service.

Frequently Asked Questions

What are the most important UX best practices?

Focus on consistent navigation, WCAG 2.1 AA accessibility (4.5:1 contrast, keyboard support, semantic HTML), minimal form fields with inline validation, Core Web Vitals performance, and touch-first mobile design with 44x44px tap targets.

What are Core Web Vitals targets for good UX?

Aim for Largest Contentful Paint under 2.5 seconds, Interaction to Next Paint under 200 milliseconds, and Cumulative Layout Shift under 0.1. These directly impact user satisfaction, engagement, and conversion.

How do you make forms more user-friendly?

Only ask for what you need, use single-column layout, place labels above inputs, validate inline as users move between fields, write specific error messages, and label the primary action button with a verb like 'Create Account.'

What is the minimum touch target size for mobile?

Apple's Human Interface Guidelines recommend a minimum of 44 by 44 pixels for touch targets, with at least 8 pixels of spacing between interactive elements to prevent accidental taps.