Website QA checklist
Run this checklist before signing off a website build. It walks through cross-browser testing, responsive behavior, form validation, link checking, and content review. These are the steps that catch the issues clients otherwise spot first.
Visual & layout
0 / 6Cross-browser
0 / 6Responsive
0 / 7Forms & interactions
0 / 6Links & navigation
0 / 6Content
0 / 5Performance & SEO
0 / 5How to use this tool
- 1Work top to bottom: visual checks first, then interactions, then edge cases.
- 2Tick items as you go. Progress saves automatically.
- 3Copy as markdown when complete to attach to your sign-off ticket.
About this tool
A QA pass is not a Lighthouse score. It is the human walk-through that catches the broken anchor link, the form that submits empty, and the layout that breaks on iPad landscape. This list is structured to find those issues quickly: visual first, then functional, then edge cases.
Related tools
Bug report template generator
Fill in a few fields and copy a clean, ready-to-paste bug report in markdown. Built for product, dev, and QA teams.
Website pre-launch checklist
A 50+ item pre-launch checklist covering content, SEO, performance, accessibility, analytics, and legal. Save your progress in the browser.
Website accessibility (WCAG) checklist
Practical WCAG 2.2 AA checklist for designers and developers. Color, keyboard, screen reader, forms, and content checks.
Website handoff checklist
Hand a finished website over to a client without follow-up panic. Credentials, training, docs, and post-launch support.
Frequently asked questions
When should I run this checklist?
Twice: once before client review, once before launch. The first pass catches obvious issues; the second catches what was introduced by last-minute changes.
How long does a full QA pass take?
For a 10-page marketing site, plan 2–4 hours. For a complex web app, plan a full day per major flow. Bookmark the page and tick items as you go.
Can I tick browser X without testing on it?
You can, but you shouldn't. Most layout bugs only show up on one engine. If you don't have access to a browser, use a service like BrowserStack. Huddlekit's canvas shows several breakpoints side by side, but it renders in your own browser, so it can't stand in for a different engine.
Does this replace automated tests?
No, it complements them. Automated tests catch logic regressions. Visual QA catches the issues automation can't see: spacing, hover states, content errors, layout drift.