Check AI-Generated HTML on a Real Phone

A desktop preview can hide the problems a mobile visitor meets first: clipped text, tiny links, slow images and a contact button covered by the keyboard.
A practical sequence
- Test the public URL on your normal phone connection. Start with the first screen, menu and primary action rather than scrolling past them.
- Try a narrow window, larger text and keyboard navigation. Check that labels remain visible and that opening a menu does not trap focus or hide the close control.
- Inspect image dimensions and loading behaviour. Use appropriately sized images and avoid loading a large decorative asset before the essential text.
- Submit only safe test data to any form you control, check the success state and confirm delivery. Remove the test record where appropriate and document any remaining limitation.
An example to adapt
Acceptance list: no sideways scrolling, legible body text, clear focus, working menu, descriptive links, useful error messages and a confirmed contact route.
Try the example in a copy or a small project before applying it to live work. Keep the working version available and record the exact change you made. For a college project or a freelance handoff, being able to explain the decision and demonstrate the result is more valuable than adding features you cannot maintain.
What to check before you finish
A screenshot proves appearance at one size. It does not prove that links, forms, focus order or loading behaviour work.
Verify the intended behaviour as well as one failure case. Record what worked, what remains uncertain and how to reverse the change. An AI-generated explanation can help you investigate, but the running project and its actual output are the evidence.