Five minutes of preparation prevents an hour of discussion about the tests.
List the pages and flows in scope
Agree the screen sizes you will check
Use real content, not placeholder text
Have the latest design files to hand
Decide how you set priorities
Step 2
Layout and spacing.
Most visual bugs are spacing bugs. Measure instead of eyeballing.
Sections line up to the same content width
Spacing between sections is consistent
Padding inside cards and buttons matches
Nothing overlaps or gets cut off
No sideways scroll at any width
Step 3
Typography.
Check the real fonts, not what the screenshot suggests.
Headings use the right font, size and weight
Line height and letter spacing match the design
No single word left alone on a last line
Long words and names wrap without breaking layout
Text stays readable at the smallest screen
Step 4
Colour and contrast.
Contrast is where accessibility and polish meet.
Body text passes AA contrast
Buttons and links pass AA in every state
Brand colours match the exact values
Disabled states still read as disabled
Images and icons hold up on dark and light backgrounds
Step 5
Interactive states.
The states nobody sees in a static design are where bugs hide.
Hover, focus and pressed states exist and look right
Menus, dropdowns and tooltips open fully
Keyboard focus is visible on every control
Loading, empty and error states have a design
Modals close and return focus properly
Step 6
Screen sizes.
Check the widths your visitors use, plus the awkward ones in between.
Desktop, tablet and phone layouts all hold
Tablet in both portrait and landscape
Navigation works at every breakpoint
Images stay sharp and correctly cropped
Tap targets are big enough on phones
Step 7
Links, buttons and forms.
Every button should go somewhere, and every form should forgive mistakes.
No link or button goes nowhere
External links open where you expect
Forms validate and explain errors clearly
Success messages appear after submitting
The 404 page helps people find their way
Step 8
Content and launch.
The last pass is about words and the details search engines read.
No spelling mistakes or leftover placeholder text
Every page has a clear title and description
Images have meaningful alt text
Legal pages and contact details are in place
Fix, test again and close each problem
FAQ
Questions
How long does a website QA pass take?
For a ten-page site, plan half a day for the first pass and an hour for the retest. Larger sites are best split by flow, such as sign-up or checkout.
Who should run website QA?
Ideally someone who did not build the page: a designer, a QA tester or the project lead. Fresh eyes catch more.
How does EasyQA help with this checklist?
You pin each finding on the exact element, with its screenshot and screen size attached. The ruler measures spacing and reads fonts and contrast. The page audit finds broken links, spelling mistakes and extra fonts in one click.